Check whether the outcome improved
Verify the all-success path
Process a batch where every selected item reaches success. Compare item count, terminal count, summary wording, and downstream eligibility. Confirm the batch does not remain partial because of a stale failure or an excluded record that was never part of the selection.
Verify mixed terminal states
Run batches with one failure, skip, and cancellation, separately and together. Check that each reason remains visible, the summary requires the documented review state, and no consumer treats mixed outcomes as all-success. Read durable records after any retry completes.
Verify missing-result handling
Stop one item before it records an outcome and let the rest finish. Confirm the batch cannot claim complete success and that the missing item has a recovery path. Repeat after a late result arrives to ensure aggregation moves to the correct terminal state.
What to carry forward
Accept when every fixture maps item outcomes to the documented batch state and downstream gate, with missing results remaining explicit until resolved. Record any intentionally unsupported combination. Reopen verification if a status label and gate disagree even when the visible counts appear correct.
Technical background: Celery documentation.
Keep the decision with the work.
Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.
Create an account See the product workflow