Every sync — manual or scheduled — creates a sync run you can review on the Sync Logs page. Each run records its trigger, direction, status, timing, and (on failure) an error summary.
Run statuses
| Status | Meaning |
|---|---|
| Queued | Waiting to be picked up by a queue worker. |
| Running | In progress. |
| Succeeded | Completed with no errors. |
| Partial | Completed, but some records failed — check the error summary for what to fix. |
| Failed | Did not complete. Check the error summary; connection and authentication problems are the most common cause. |
| Cancelled | Stopped before finishing. |
Triggers
A run's trigger tells you why it happened: manual (you clicked sync), scheduled (it was due per its sync frequency), or internal (triggered by the system, e.g. a chained feed-to-feed sync).
Diagnosing a failed sync
- Read the error summary on the failed run first — credentials, secrets, and tokens are automatically redacted, so it's safe to share while debugging.
- Use the channel's connection test before re-running a sync, to rule out an expired credential or an unreachable endpoint.
- For a partial run, check whether specific products are missing required fields for that destination (a common cause of per-record failures).
- A stuck "running" sync is automatically recovered by the platform's periodic stale-run check, so it won't block the next scheduled run indefinitely.