> For the complete documentation index, see [llms.txt](https://docs.violetlabs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.violetlabs.com/features/workflows/data-sync-workflows/approve-and-monitor-syncs.md).
# Approve and monitor syncs
## **Pending changes**
If you choose to execute your sync workflow on a *schedule* or on *approval*, Violet won't apply changes directly — it will generate **Pending Changes** for you to review first.
* After a workflow run, open the **Pending Changes** tab to see what will be created, updated, or deleted
* Each batch shows a breakdown by change type before anything is applied to the target system
* Once a sync batch is executed (following your approval or per the established schedule), it moves to **Sync History** with a full record of what succeeded, failed, or was skipped.
Entity-by-entity sync change data is visible as Pending Changes before a sync has been executed, or in the Sync History after a sync has occurred. You can use the keyword search bar above the table, or filter/order the columns in the table by clicking on the column header to find specific entries that you want to verify or investigate.
Clicking any row in the table will show you the details of which properties have been updated, and list all the properties that have remained unchanged.
## Sync history
Sync History is organized by *Batches*. In each Sync Batch you will see all of the sync changes and their status.
For any entity syncs that **Failed** or were **Skipped**, the details will explain the reason for the failure or why that entity was skipped. Failures sometimes occur due to missing permissions or data completeness problems, which can typically be fixed by the user.
Skipped syncs are common - if an entity did not sync because of your workflow filtering configuration, or none of the properties that you mapped between your source and target have changed, it will have a status of "Skipped"
---
# 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.violetlabs.com/features/workflows/data-sync-workflows/approve-and-monitor-syncs.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.