Skip to main content
You can trigger a new execution for any of your clients at any time from their consumer page. To run the synchronization, simply click the play button next to the sync. When you click this button, there are two possible scenarios:
  1. Your sync does not support manual execution for a specific period.
  2. Your sync supports manual execution for a specific period.

Your sync doesn’t support manual execution for a specific period

If your sync doesn’t support manual execution for a specific period, the following tab will open when you click the play button: From here, you can simply click Execute to start the sync for your client.
This will run the default synchronization.

Your sync supports manual execution for a specific period

In this case, you can either run the default synchronization or run it for a specific date. (If this view doesn’t appear when you click the play button, it means this feature hasn’t been implemented yet for your sync. Please reach out to your CSM.) The self-service feature lets you choose between the following options:
  • Synchronize all missing data (don’t re-import data that’s already been synchronized).
  • Synchronize all data for a specific date, as if nothing had been imported before.
  • Synchronize all data for a specific date range, as if nothing had been imported before.

Run the default synchronization

To run the default synchronization (which won’t import anything that’s already been imported), simply click Execute without changing anything on this tab.

Force synchronization for a specific date

To run the synchronization for a specific date, click the Single Date tab, select the date you want to import, and click Execute. Note that this will import all data, even if it has already been imported before. You must make sure with the client that the data can be safely re-imported; otherwise, the data will be duplicated in their tool. If you’ve received confirmation from the client, check the “I confirm” checkbox and click Execute to start the synchronization.

Force synchronization for a date range

To run the synchronization for a range of dates, click the Date Range tab, select the desired dates, and click Execute. You’ll then be asked what needs to be imported:
  • If you only want to import missing data, simply click Execute and the sync will start immediately.
  • If you want to re-import all data for that date range, select the second option. If data was already imported for that date range, you will see an alert asking you to confirm the import of data.
    Make sure with the client that this is acceptable, otherwise this might result with duplicate data into your tool.
    Check the “I confirm” checkbox and click Execute to start the synchronization.

Execution statuses

Each execution is assigned a status that reflects its current state or final outcome. These statuses help you quickly determine whether the synchronization completed successfully or requires attention.

IN PROGRESS

The execution is currently running.
  • The sync has been triggered and is actively processing.
  • Logs and results may still be incomplete.
  • The status will update automatically once the execution finishes.

FINISHED

All good — no errors occurred.
  • The execution completed successfully.
  • All steps were processed without validation or technical errors.
  • No corrective action is required.
This is the expected status for a healthy synchronization.

FINISHED ⚠︎

Completed with non-fatal errors.
  • The execution finished processing.
  • One or more issues occurred (for example, validation errors or partial rejections).
  • No fatal or system-level error interrupted the execution.
Typical examples:
  • Validation errors on specific records
  • Business rule violations
  • Non-blocking data inconsistencies
The synchronization completed, but reviewing the execution details is recommended.

ERROR

Execution failed due to a fatal error.
  • The sync could not complete successfully.
  • A critical issue interrupted the process.
Typical examples:
  • Authentication or authorization failures
  • Connectivity issues
  • Technical or system exceptions
  • Configuration errors
Investigation is required. After resolving the root cause, the execution should be retried.

CANCELED

Execution was manually stopped.
  • The sync was intentionally canceled before completion.
  • No further processing occurred after cancellation.
This status typically results from manual user intervention or administrative action.