> 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**

Every time a workflow runs, Violet generates **Pending Changes** for you to review — nothing is applied to the target system until the changes are executed. When they're executed depends on the integration pair's execution mode: never in **Test Mode**, on a schedule with **On Timer**, or after approval or completion of selected workflows with **On Activity**.

* After a workflow run, open the **Pending Changes** tab to see what will be created, updated, or deleted
* The metrics at the top show the total number of changes and the breakdown by change type (**Created**, **Updated**, **Deleted**) 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. To find specific entries that you want to verify or investigate, you can:

* Use the keyword search bar above the table
* Filter by **Status** (Pending, Executing, Success, Failed, Skipped, Dry Run) or **Change Type** (Create, Modify, Delete), and click **Reset filters** to clear them
* Filter or order the columns by clicking on the column header, and show or hide columns from the **Columns** panel
* Export the table with the download icon

Alongside each change's status, the table shows its **Validation** result, **Conflict / Alignment**, and the property-level **Diffs**.

<figure><img src="https://2091741164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvrraExym8pNEUvBDoima%2Fuploads%2F4A2jQuWyjNjKBRG07iT5%2Fimage.png?alt=media&amp;token=70572e20-1005-428f-ade6-ec0cf7e2154f" alt=""><figcaption></figcaption></figure>

Clicking any row opens the change details: a table comparing each attribute's **Source** and **Target** values, plus **Debug notes** and the change's **Validation** status.

<figure><img src="https://2091741164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvrraExym8pNEUvBDoima%2Fuploads%2FJpotEc7aO3jxG1aULjki%2FScreenshot%202026-05-12%20112022.png?alt=media&amp;token=1a07cc1c-41e4-40e2-9f8b-6db05c961c35" alt="" width="255"><figcaption></figcaption></figure>

### Executing or rejecting the batch

Use the buttons above the table to act on the whole pending batch:

* **Execute** — execute the pending changes in the target system
* **Reject** — mark all pending changes as rejected. This cannot be undone.
* **Timeline** — view the timeline of pending changes

### Acting on an individual change

Each row has two actions in the right-most column:

* **Execute this change** (arrow icon) — immediately executes that single change in the target system. For a forced execution like this, the automatic target integration fetch afterward is skipped.
* **Force re-create this change** (sync icon) — regenerates the pending change.

{% hint style="warning" %}
**Execute this change** writes to the target system right away, even before the rest of the batch is approved.
{% endhint %}

## Sync history

Sync History is organized by *Batches*. In each Sync Batch you will see all of the sync changes and their status. Use the status filter (Approved, Rejected, In Progress, Completed, Failed, Cancelled), the start and end date fields, and the **Include empty batches** toggle to narrow the list. The metrics at the top show total, completed, approved and rejected batches.

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"

<figure><img src="https://2091741164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvrraExym8pNEUvBDoima%2Fuploads%2Fv2ObEOhS6iaDHzRjPyfx%2Fimage.png?alt=media&amp;token=32a03b44-b354-4d1d-b521-5957af5153af" alt=""><figcaption></figcaption></figure>

## Sync Report

The **Sync Report** tab lists every sync change identified within a date range (the last 7 days by default). You can view changes as a **Tree** (descendants nested under their parent), **Flat** (every change as its own row), or **By Batch** (grouped by sync batch), search by keyword, filter by status and change type, and export the table.

## Sync Validation

After a sync is executed, Violet performs a validation process to compare what we intended to do against what was actually implemented in the target system. The following validation values may be returned:

* Failed — Violet compared values and they don’t match (drift), or delete validation failed (e.g. item should be deleted but isn’t).
* Passed — Comparison ran and everything matched.
* Superseded — A newer sync change for the same target replaced this one; validation on the old row was intentionally skipped.
* Pending — Validation hasn’t run yet (often waiting for the target integration to fetch fresh data).
* Inconclusive — Something prevented Violet from completing the validation.

Note: a sync change can show Success for execution and Inconclusive for validation.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.violetlabs.com/features/workflows/data-sync-workflows/approve-and-monitor-syncs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
