> For the complete documentation index, see [llms.txt](https://docs.verbdata.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verbdata.com/data-sources/data-synchronization/synchronization-history.md).

# Synchronization History

Verb keeps a rolling 30 day audit log of all the interactions with your data source.  Each time our system connects to a database or reads from a cloud-hosted file, our system logs the success or failure of that interaction.  If you're data source is configured to synchronize data every hour, then your data source will have 24 historical log entries per day.  These entries are a sign of the overall health of the data synchronization process.

When errors occur, Verb will attempt to handle the issue and fall back gracefully.  For example, if one table cannot be read (for example due to column changes), the remainder of the tables will still be queried.  You can follow our [troubleshooting steps](/data-sources/data-synchronization/troubleshooting.md) to diagnose and fix any issues that occur.

Clicking any object (table) in your data source will show the last 24 hours of synchronization history by default.  You can view previous synchronizations day by day.  

![](/files/SNvDZ63y5pXIJcCtgSto)

The 30 day view gives a broader picture of the success over time and can help to identify periodic failures that may arise.

![](/files/j5EKOeGe7UJ0rguMRvRc)


---

# 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.verbdata.com/data-sources/data-synchronization/synchronization-history.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.