PECI Worker Skipped — Unprocessed Prior Event
The error Worker 12345: 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 (unconfirmed payroll input, an in-progress business process, or an unacknowledged previous extract), so the connector won't emit the newer change until the earlier one resolves — otherwise the payroll system would receive changes out of order.
Troubleshooting
- Open the worker's event history and look for in-progress or rescinded-but-unprocessed events before the stuck change's effective date.
- Check whether the downstream payroll acknowledged the previous PECI file (missing ACK can hold the worker in a pending state).
- Review the PECI run history for the worker across the last few extracts — the first failed/missing extract usually marks 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 emit in order.
✓ Permanent fix
Monitor BP queues for events older than the payroll cutoff, enforce the acknowledgment flow with the payroll vendor, and add a pre-payroll-deadline report of workers with in-progress events so blockers are cleared before the extract runs.