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 actually an error - the connector checked its transaction log and found no worker changes matching the integration's population and field scope since the last successful run. It becomes a problem when downstream expects a file, or when changes did happen but got filtered out.
Troubleshooting
- Confirm whether changes actually occurred in the window - check the last successful run timestamp the connector is diffing against.
- Review the population filter - 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 - check the run history.
⚡ Quick fix
Enable full-file output for one run (or send an empty-file header per the downstream spec) and verify the next delta run picks up normally.
✓ Permanent fix
Agree an empty-file contract with the receiving system, document the change-detection window behavior, and add a note covering rerun scenarios so the delta window is never silently consumed.
Was this helpful?