Organized by pipeline stage—overall (initialization), extract, transform, or load—Celigo sync run errors clearly point to where a failure occurred. This article walks you through locating these errors, identifying the responsible stage, and taking the necessary steps to resolve or escalate the issue so you can restore a clean run as quickly as possible.
Unlike error handling in application integrations, data ingestion errors are tied to the sync run rather than to individual records: you don't hold, edit, or retry records one at a time. Instead, you fix the underlying cause and let the next run clear the errors.
Review sync run errors
Review errors for a sync's latest run, alongside job run history.
- Go to Home
, and then open the integration containing your sync.
- Select the sync name to open the sync dashboard.
- Errors appear in the graph and in the run table. Select the error count to see details, or select Actions (...) > View details on a run's row to see the errors for a specific table.
Error details are consolidated at the run level, but you can select a run to view errors for individual objects, like specific destination tables. If the most recent run fails, the error count also displays next to the sync in the Home page's sync list and on the integration tile.
How sync errors are organized
Errors are categorized by the sync stage in which they occur: overall (initialization), extract, transform, or load. Identifying the active stage tells you whether you can resolve the issue yourself or need Celigo support. Sync errors are temporary — because error counts don't persist across run lifecycles, a successful run, whether scheduled or manually triggered, automatically clears them.
| Stage | Typical causes | Resolution |
|---|---|---|
| Overall (initialization) | Initialization flow failure, metadata extraction failure. | Re-run the sync, or wait for the next scheduled run. |
| Extract | Connection down, insufficient permissions, API rate limits on the source. | Restore connectivity, adjust permissions, or wait for the rate limit to reset, then re-run the sync or wait for the next scheduled run. |
| Transform | Mapping failures, data type conversion failures. | May point to an internal Celigo issue — contact Celigo support. Re-running is likely to keep failing until Celigo resolves the issue. |
| Load | The sync extracted data but couldn't write it to the destination: bulk load failure, file generation failure, storage (S3) failure, or destination data warehouse issues (for example, data quality violations, or the warehouse running out of credits). | Re-run the sync — the re-run performs a fresh extract as well as the load. |
How a run progresses — and what happens when it fails
A sync run's stages execute one after another: extract, then transform, then load. The stages don't overlap, and a failure at any point ends the run — a failure during load discards all of the run's progress, and the next run restarts from extract.
Note
Failed runs are not retried automatically. Celigo sync does not auto-retry a failed run; you must re-run the sync manually or wait for the next scheduled run, which starts over from extract.
Verify the resolution
After making a change, confirm the fix by starting a manual run or waiting for the next scheduled run. A run that completes without errors confirms the issue is resolved.
Prevent missed errors
Set up error notifications so you learn about failed runs without checking the dashboard. Configure notifications at the sync level or the integration level (see Edit or view a sync's settings).