> For the complete documentation index, see [llms.txt](https://docs.aohwv.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aohwv.dev/feature-reference/connectors/logs.md).

# Sync History

The Sync History view shows a time-ordered log of every inbound Sync run for this Connector, so you can confirm that data is flowing correctly and investigate any failures.

![The Sync History view for AOH Test AD → CloudSync (Delta), showing a table of recent sync runs with columns for Started, Status, Duration, Records, and Detail](/files/S1OBiEcvmmPCDFtl1XqV)

*The Sync History table lists recent Sync runs with their start time, status, duration, record count, and detail.*

## What you can do here

| Action          | What it does                                                                                                                                                            |
| --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Refresh         | Manually reloads the Sync History table. The view updates automatically every 5 seconds.                                                                                |
| Review run rows | Each row shows the start time, outcome status, how long the run took, how many records were processed, and an additional detail column indicating the sync method used. |

## Understanding the Sync History table

Each row in the Sync History table represents one completed or in-progress Sync run:

* **Started** — The date and time the Sync run began.
* **Status** — The outcome of the run. Typical statuses include **succeeded** (completed without errors) and **running** (currently in progress).
* **Duration** — How long the Sync took to complete, shown in seconds.
* **Records** — The number of records processed during this run. A dash (—) indicates that record-level counts were not captured for that run.
* **Detail** — Additional context about the run, such as the method used to retrieve data (for example, `via entra_id`).

{% hint style="info" %}
The Sync History view updates automatically every 5 seconds. Click **Refresh** at any time to load the latest data immediately.
{% endhint %}

## Related

* [Sync Types](/core-concepts/sync-types.md)
* [Schedule](/feature-reference/connectors/schedule.md)
* [Revisions & History](/feature-reference/connectors/revisions.md)
* [Connector Overview](/feature-reference/connectors/overview.md)
* [Connectors](/feature-reference/connectors.md)


---

# 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.aohwv.dev/feature-reference/connectors/logs.md?ask=<question>&goal=<endgoal>
```

`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.