> For the complete documentation index, see [llms.txt](https://docs.cipp.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cipp.app/user-documentation/cipp/integrations/integration-sync.md).

# Integration Sync

This page lists the scheduled synchronisation tasks that push CIPP's cached tenant data out to your configured integrations, along with when each one last ran and what the result was. It is the quickest way to confirm that an integration is actually syncing rather than silently failing.

Only integrations that register a recurring push task appear here. In practice that means Hudu and Custom Data, each of which gets one task per mapped tenant. Integrations that sync on demand or through their own orchestrator, such as NinjaOne and Gradient, do not create tasks in this table. If you have upgraded from an older release you may briefly see legacy sync tasks listed; these are removed automatically the next time the sync tasks are registered.

## Table Details

| Column         | Description                                                                                                                         |
| -------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| Tenant         | The tenant the sync task runs for. Each mapped tenant gets its own task.                                                            |
| Sync Type      | The integration the task belongs to.                                                                                                |
| Scheduled Time | The relative time until the next run.                                                                                               |
| Executed Time  | The relative time since the task was last picked up.                                                                                |
| Repeats Every  | The recurrence of the task. Extension sync tasks are registered to run daily.                                                       |
| Results        | The outcome of the last run. Where the task recorded structured output, it is shown as an expandable object rather than plain text. |

The underlying task name, for example `Hudu Extension Sync`, is also returned and can be shown by adding the **Name** column.

{% hint style="info" %}
Scheduled tasks are picked up on the quarter hour (:00, :15, :30, :45). Anything due or overdue is collected at the next quarter hour, so the Scheduled Time tells you which one your task will land on rather than the exact minute it will run.
{% endhint %}

{% hint style="warning" %}
Tasks are created and removed automatically when you change an integration's tenant mappings, so there is nothing to add or delete here. A tenant disappearing from this table usually means its mapping was removed rather than that the sync has broken.
{% endhint %}

***

## Feature Requests / Ideas

We value your feedback and ideas. Please raise any [feature requests](https://github.com/CyberDrain/CIPP/issues/new?template=feature.yml) on GitHub.


---

# 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.cipp.app/user-documentation/cipp/integrations/integration-sync.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.