Sync logs
Sync logs are the per-run record of a source's sync, showing whether a specific run succeeded, failed, or was skipped.
Category
Product feature
See all terms
What are sync logs?
Sync logs are the record generated by every run of a sync: a timestamped entry showing when that run started, when it finished, what its status was, and what it pulled in. Each connected source keeps its own sync logs, viewable from that source's tab, so a workspace can check any run of any connector.
Why do sync logs exist?
A sync is the ongoing process that keeps a source's data current in the context repository. A sync log is not that process, it's what that process leaves behind each time it runs. Sync logs differ from retrieval logs: retrieval logs record what a client read out of the context repository, while sync logs record what came into it from a connected source. Keeping the two separate matters because a failed sync and a bad retrieval look identical from an agent's wrong answer, and only checking the right log tells you which one happened.
How do sync logs work?
Every sync run creates a sync log entry with a status. Each entry also records the sync's type, when it started and completed, how many records it expected to ingest against how many it actually ingested, and an error message if it failed. Checking sync logs after a large or first-time sync confirms it succeeded and surfaces configuration or permission issues early, since a first sync can take up to 12 hours. If a sync fails, triggering another sync is the first fix; please reach out directly if a sync keeps failing. Sync logs are available through the API, which returns the same fields, status, type, timestamps, record counts, and pipeline identifiers, for programmatic monitoring, so the context repository's inflow can be audited the same way its outflow is audited through retrieval logs.