> For the complete documentation index, see [llms.txt](https://docs.abtasty.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.abtasty.com/recommendations-and-merchandising_deprecated/recos-and-merch-account-management/how-to-manage-synchronisations.md).

# How to manage synchronisations

## Accessing the Synchronisations Tab <a href="#h_01jdq0y7je9jjtwg852vm8te46" id="h_01jdq0y7je9jjtwg852vm8te46"></a>

1. Navigate to the **Syncs** tab in **Settings**, located at the bottom of the left-hand menu.
2. Alternatively, access it by clicking on the **last update button** at the top of the screen.

![](https://2350286830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6Yw9IRJ6KbbucQPwZUCZ%2Fuploads%2Fgit-blob-3e8dad32e86296f4cc687cc8a6ad283f728f650a%2Fa98335f22d9445ea541fd53f62953ce8.png?alt=media)

## Overview of Synchronisations <a href="#h_01jdq0y7je7b8n3a2rs5qy3m87" id="h_01jdq0y7je7b8n3a2rs5qy3m87"></a>

On the synchronisation page, you can view all synchronisations associated with your account. The page provides details on:

* **Status**
* **Type**
* **Duration**
* **Automatic Refresh**:
  * The data on this page is refreshed automatically every **15 seconds** to ensure it stays up to date.

## Synchronization Details <a href="#h_01jdq0y7jechpr0hmnv69rs97x" id="h_01jdq0y7jechpr0hmnv69rs97x"></a>

| **Field**        | **Description**                                        |
| ---------------- | ------------------------------------------------------ |
| `id`             | Unique identifier (UUID).                              |
| `siteId`         | ID of the entity site.                                 |
| `type`           | Synchronisation type (`SynchronizationType`).          |
| `status`         | Synchronisation status (`SynchronizationStatus`).      |
| `infos`          | JSON containing additional details.                    |
| `createdAt`      | Timestamp of synchronisation creation.                 |
| `endedAt`        | Timestamp of synchronisation completion.               |
| `updatedAt`      | Last updated timestamp.                                |
| `deletedAt`      | Timestamp of synchronisation deletion (if applicable). |
| `runner`         | System runner for the process (e.g., “kubeflow”).      |
| `createByUserId` | ID of the user who initiated the process.              |

* **Note**: All fields are automatically set by the system.

## Types of Synchronisations <a href="#h_01jdq0y7jfgvcd7cjmr6wpraky" id="h_01jdq0y7jfgvcd7cjmr6wpraky"></a>

1. **Resources Updates**:
   * Synchronises the **catalog**, **recommendation products**, and **analytics data**.
   * Can be launched:
     * At fixed intervals pre-defined by AB Tasty recommendation & merchandising.
     * Manually by clicking the **“Run Synchronization”** button.\
       ![](https://2350286830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6Yw9IRJ6KbbucQPwZUCZ%2Fuploads%2Fgit-blob-00bbecf2c9af0831c231dda989d40f780f191374%2F8c2bf6220f53e095728e1e062e02e4cd.png?alt=media)
2. **Recommendation Products Updates**:
   * Automatically triggered when changes are made to the configuration of an experience (e.g., modifying a recommendation).

## Synchronisation Statuses <a href="#h_01jdq0y7jfk74xtvwnafx94f72" id="h_01jdq0y7jfk74xtvwnafx94f72"></a>

Synchronisations can have one of the following statuses:

* **Scheduled**: Created but not yet running.
* **Running**: Currently in progress.
* **Succeeded**: Successfully completed.
* **Failed**: Stopped due to an error.

## How to Run a Synchronisation <a href="#h_01jdq0y7jfr0c0s98pxpy353h4" id="h_01jdq0y7jfr0c0s98pxpy353h4"></a>

1. Navigate to the **Syncs** tab in **Settings**.
2. Click on the **“Run Synchronization”** button to manually trigger the process.


---

# 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.abtasty.com/recommendations-and-merchandising_deprecated/recos-and-merch-account-management/how-to-manage-synchronisations.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.
