errors / core-connectors / core-connector-no-output-change-detection
Core Connector Produced No Output (Change Detection)
The error Integration event completed. 0 records written to output. Change detection found no eligible changes since last successful run.
What it means
Not an error in the strict sense: the connector's transaction-log/change-detection window found no worker changes that match the integration's population and field scope since the last successful run, so the output file is empty. It becomes a real problem when downstream expects a file or when changes did happen but were filtered out.
Troubleshooting
- Confirm whether changes actually occurred in the window: check the last successful run timestamp the connector is diffing against.
- Review the integration's population filter (eligibility) — a worker who changed but left the population produces nothing unless the connector is configured for removals.
- Check which fields are enabled in the field configuration: changes to non-included fields don't count.
- If a previous run was force-completed or rerun, the change window may have been consumed — look at the run history.
⚡ Quick fix
If downstream needs a file every run, enable full-file output for one run (or send an empty-file header per the spec) and verify the next delta run picks up normally.
✓ Permanent fix
Agree the empty-file contract with the receiving system (send empty file vs skip), document the change-detection window behavior, and add a launch parameter or schedule note covering rerun scenarios so the delta window is never silently consumed.