Sync history

Sync history is the engine’s log: one row per cycle, showing when it ran, what triggered it, how it ended, and what it moved. Open a row for the per-item detail, including why anything was skipped and the other tool’s own error text.

It also tracks continuity: a window of change in the other tool that no cycle ever read is flagged as a gap, which is the one thing this log knows that nothing else does.

What it is not

• It is not the audit trail. An inbound change to a controlled item lands through the same save path as a person’s edit — a new version of the item and an audit entry, attributed to the mapped individual. That is the durable record. Sync history says how the cycle went, and the screen labels itself as operational so it is never cited as evidence.
• It is not a control panel. Nothing here starts or retries a sync. You run an integration from the integration, and retry a failed write from Activity, so the record of what happened is never also the place things are made to happen.

How long it is kept

Cycles are kept for 90 days unless an administrator sets another window, from 7 days up to 10 years. Delivered writes are kept for 30 days by default; the fact of a delivery stays on the link permanently.

Exporting

The log can be exported. An export is refused rather than silently truncated when the selection is larger than one export can carry.

Who can open it

Sync history is available to organisation administrators and quality managers. Each sees only the projects they can read, and the screen says so when the view is partial.