PECI Worker Skipped: Unprocessed Prior Event
The error Worker [ID]: change not processed. A prior effective-dated event for this worker is pending in an unconfirmed state.
What it means
PECI builds per-worker deltas in effective-date order. This worker has an earlier event still pending - an in-progress business process, unconfirmed payroll input, or an unacknowledged previous extract - so the connector won't emit the newer change until the earlier one resolves.
Troubleshooting
- Open the worker's event history and look for in-progress or unprocessed events before the stuck change's effective date.
- Check whether downstream payroll acknowledged the previous PECI file - a missing ACK can hold the worker in a pending state.
- Review the PECI run history for this worker across the last few extracts to find where the chain stalled.
- Confirm the business process that created the earlier event is actually completed, not sitting on an approval step.
⚡ Quick fix
Complete or cancel the blocking event (or process the missing acknowledgment), then re-run the extract. The held changes will emit in order.
✓ Permanent fix
Monitor BP queues for events older than the payroll cutoff. Enforce the acknowledgment flow with the payroll vendor. Add a pre-payroll-deadline report of workers with in-progress events so blockers get cleared before the extract runs.
Was this helpful?