> For the complete documentation index, see [llms.txt](https://docs.fastn.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fastn.ai/operate/sync-reports.md). # Sync reports What changed on the last run of each sync, record by record. **Activity → Sync reports** Executions tell you a run succeeded. Sync reports tell you what it did, record by record. ### How a report is produced > A report appears the first time a workflow runs `fastn.diff.compare`. Which implies reports are effectively opt-in at the workflow level: a workflow that compares its source and target through `fastn.diff.compare` produces one, and a workflow that does not, does not. ### What it is for The gap between "the run succeeded" and "the data is right" is where support tickets live. When a customer says records are missing, this is the page that distinguishes *the record was filtered out* from *the record was never seen*, which the executions log cannot tell you. Each workflow also has a **Sync reports** tab in its editor, scoped to that workflow, with the same empty-state note. ### Controls **Search reports**, and nothing else. Unlike Events, Traces and Executions, this page has no status filters and no date range. Until a workflow has run `fastn.diff.compare`, the page reads **No sync reports yet**. {% hint style="info" %} This page is thin in these docs because no sync report had been produced in the workspace we documented from: the shape of a populated report is not something we can describe accurately. If you are building a data sync and this page stays empty, ask the agent to add diff reporting. It is far easier than reconstructing what a run did from logs afterwards. {% endhint %} --- # 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.fastn.ai/operate/sync-reports.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.