How to manage synchronisations

Accessing the Synchronisations Tab

  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.

Overview of Synchronisations

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

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

  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.

  2. Recommendation Products Updates:

    • Automatically triggered when changes are made to the configuration of an experience (e.g., modifying a recommendation).

Synchronisation Statuses

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

  1. Navigate to the Syncs tab in Settings.

  2. Click on the “Run Synchronization” button to manually trigger the process.

Last updated

Was this helpful?