Reading sync history
When somebody asks why an invoice reached the accounts twice, or not at all, this is where the answer is.
- How to narrow the list and open a run
- The four statuses, and which of them need opening
- Why each table also has its own smaller log
- How far back it goes, and what you cannot clear
01 · Why
Why do we have this?
It is the audit trail. When somebody asks why an invoice reached the accounts twice, or not at all, this is where the answer is.
02 · How
Read the history
- Open
Sync Statuson the connection. - Use
All entitiesandAll statusesto narrow the list. - Click any row to expand it and see per-record detail.
03 · Expected result
Each row shows the time, the direction, the record type, how many were processed, how many failed, how long it took, and a status.
| Status | What it means |
|---|---|
| Completed | Everything went through. |
| Partial | Some of it did not. Expand the row. |
| Failed | Nothing went through. |
| Running | Still going. |
04 · Notes
Expand anything that is not Completed
The Failed column is not dependable — see Why a record did not reach your accounting system.
Each table has its own smaller log
The Integration Logs tab on a connected table shows just that table's activity, in plainer language — for example Sync completed — Customer · 29 records synced in 4s. It also has date filters.
05 · FAQ
Common questions
Everything on that connection. Ours held runs from two months earlier.
No.
Expand it. It usually means records were rejected without being counted.