Sync logs

A record of every sync: what ran, what changed, and what failed.

The list

Each row is one sync, whether you started it, a schedule did, or a change in the connected system triggered it. A row shows:

• Sync: the connected system and what it synced, such as Shopify · Products, then what started it (Manual, Scheduled, Webhook, or Onboarding) and the language when the sync covered a single one.
• Status: Running, Completed, Completed with errors, or Failed. Completed with errors means some items failed while the rest came through.
• Started and Duration.
• Result: how many items were created, updated, left unchanged, or failed. Pending items are still being finished in the background, for example prices.

While something is syncing, a Syncing now panel above the list shows which syncs are running and for how long, and how many syncs and price updates are still waiting. It disappears when everything is finished.

Use the Needs attention tab to see only syncs with failures, and Running for syncs in progress. You can also filter by what started the sync. The page refreshes on its own while anything is running.

Open a sync

Select a row to see:

• The error, if the whole sync stopped.
• A count of each result.
• What was synced, one line per type, when a sync covers several. A type that failed shows its own error here.
• The items, on tabs: Failed, Changed (created or updated), Pricing when the sync updated prices, and All. The tab opens on Failed when anything failed. Search finds an item by name.

Select an item to see its message and the exact changes the sync made to it. An item that failed on its first import has no Source yet, so it shows the name it had in the connected system.

Retry

A catalogue sync that ended with errors has a Retry sync button. It queues the same sync again, and the new run appears in the list once it starts. An Available days check is run again from Automations.

A failed item has a Retry button that syncs just that item again. An item that failed on its first import has no Source yet, so it has no button; use Retry sync for those.

What is recorded

Syncs from your integrations, resyncs of a single Source, and updates the connected system sends on its own: a Shopify product that changed, a price change, a product that was removed, archived, or made active again, and a Bókun experience update. A Bókun Available days check is listed as Bókun · Available days.

Shopify stock-only updates are applied without an entry.

Entries are kept for 14 days.

When a sync fails

If Rubikc is briefly too busy to finish a sync, it tries again on its own, up to twice. Each try is its own entry, marked Retry 1 or Retry 2, and the sync only counts as failed once the last try does.

For any other failure, the message usually says why. The most common cause is a connection that needs re-authorising — reconnect it in Integrations.

After a failure

Fix the cause, then run the sync again. A sync only brings data in, so re-running one is safe.

For problems turning synced material into cubes, see Transform logs.