Process valid records and report individual refusals
Purpose
Background processing preserves successful work while identifying records that need correction or a later retry.
How It Works
Workers process a job in batches and check its state before continuing. They recheck the submitter’s permission so withdrawn access stops later work. Each successful change commits with a receipt. Redelivery consults those receipts instead of applying the same change again. Individual validation failures become coded outcomes while other records proceed. Database refusals trigger smaller commit units that isolate the failing record. Atomic groups remain a single success or refusal unit. The rejection guard pauses a job with a high cumulative refusal rate. Temporary database problems can be retried, while a systemic problem produces a failure summary. Staff inspect the resulting outcomes to decide what needs correction.
Relationships
- Submission supplies the retained input.
- Job controls govern interruption and recovery.
- Progress inspection exposes the recorded outcomes.