> For the complete documentation index, see [llms.txt](https://docs.enapi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enapi.com/data-quality/the-sync-activity-log.md). # The Sync Activity Log Below the Data Quality table, the Sync Activity Log shows a chronological list of recent sync jobs.

Sync Activity Log — recent sync events with expected vs. actual object counts.

### What it shows * **Started At.** When the sync process began (UTC). * **Finished At.** When the sync process completed (UTC). * **Platform.** The OCPI handshake the sync ran against. * **Module.** The data type synced (locations, tariffs, tokens, sessions, or CDRs). * **Result.** Objects synced / objects expected. A green checkmark means the counts match; an orange warning icon means there's a discrepancy. ### What "Success" means A sync job is marked **Success** when ENAPI completed the full request cycle against the partner's endpoint without errors — all pages were retrieved, responses parsed, and returned objects stored. It does **not** mean every individual object was valid. Objects that fail validation are stored with a flag but don't cause the sync to fail. If you see Success but the count isn't what you expect, the issue is at the object level, not the sync level. See [Common Data Quality Issues and Fixes](/data-quality/common-data-quality-issues-and-fixes.md). A sync is marked **Failure** when ENAPI couldn't complete the cycle — connection timeout, auth rejection, malformed response, or a partner endpoint returning a non-2xx status. ### Common sync patterns * **Healthy connection:** Regular Success entries. Mon–Sat for deltas, Sundays for full sync. * **Intermittent failures:** Occasional Failure, usually recovers on the next cycle. Common under partner maintenance. * **Persistent failures:** Multiple consecutive Failures on the same handshake — check endpoint reachability, Token C validity, and the OCPI responses being returned. * **No sync entries:** Handshake may not be completed, or has been disconnected. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.enapi.com/data-quality/the-sync-activity-log.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.