Understanding Sync Status and Lifecycle Substatus
Shipped: August 12, 2026 — Available on all accounts.
NinjaCat now surfaces a lifecycle substatus alongside the coarse sync status in Sync Details and Sync History, giving you more visibility into exactly what a sync is doing — and why it may be taking time.
What Changed
Sync Details — Status Column
The status column in Sync Details now shows two pieces of information:
- Coarse status — the overall state of the execution:
In Progress,Complete,Error, orNo Data. - Substatus — a human-readable description of what the sync is currently doing (for active and recently completed runs).
Substatus labels
| Coarse Status | Substatus shown |
|---|---|
| In Progress | Ingesting data |
| In Progress | Staging data |
| In Progress | Finalizing data |
| Complete | (none — no substatus shown) |
| No Data | (none — no substatus shown) |
| Error | Failed during: {stage} |
- Ingesting data — NinjaCat is actively fetching records from your data source.
- Staging data — Fetched data has been received and is being prepared for processing.
- Finalizing data — Data has been staged and is being written to your dataset.
- Failed during: {stage} — The sync encountered an error at the named stage (e.g., Failed during: Ingesting data).
Timing signals
For runs that have lifecycle substatus data, you will also see:
- Time in current stage — how long the execution has been in its current lifecycle stage.
- Last activity — a signal indicating when the sync last made progress.
These signals help you distinguish a sync that is actively working from one that may be stalled.
Sync History — Improved Status Accuracy
Two status values in Sync History have been corrected to more accurately reflect what happened during a run:
| Previous label | New label | When shown |
|---|---|---|
| Complete | No Data | The batch completed but returned zero records |
| Complete | Complete with Errors | The batch finished but some (not all) records encountered errors |
Complete now means the batch finished successfully with records and no errors.
What You May See During the Transition
Lifecycle substatus data is only available for runs that occurred after August 12, 2026. Older runs will continue to show the coarse status (In Progress, Complete, Error, No Data) with no substatus or timing details — this is expected behavior, not a bug.
During the transition period, it is normal to see a mix of:
- Detailed rows (with substatus and timing) for recent runs.
- Rows with coarse status only for historical runs.
No action is required on your end.
Frequently Asked Questions
Why does a run show "In Progress" with no substatus?
This run started before August 12, 2026 and does not have lifecycle stage data. It will display only the coarse status.
Does "No Data" in Sync History mean something went wrong?
No. "No Data" means the batch completed normally but there were no records to ingest for that time range — for example, if your data source had no activity during that period.
What does "Complete with Errors" mean?
Some records in the batch encountered errors during processing, but the batch as a whole was not fully blocked. Data may be partially available. Review the individual run details for specifics.
Can I see how long a sync waited before it started fetching data?
Not yet. Visibility into the pre-dispatch and orchestration wait time (the time before a sync begins fetching data) is planned for a future release and is not part of this update.
Are these status fields available in the API?
Yes. Lifecycle stage fields are now included as backwards-compatible additions on the existing execution APIs. No changes to existing integrations are required.
Related Articles
Updated about 2 hours ago