Establish what is happening
Build the item outcome ledger
List every selected item and assign the recorded result, attempt count, and terminal timestamp. Include one known failure and one skipped item if the workflow supports them. Mark missing outcomes separately instead of folding them into a generic incomplete count.
Compare summary and item states
Read the batch status, counts, failure reasons, and downstream eligibility beside the ledger. Check whether completion means all items succeeded, all attempts ended, or merely that the worker stopped. Save the exact label and update time shown to the reader.
Locate the unsafe handoff
Follow the summary into the next action, such as release, export, or notification. Determine whether that action starts on any terminal batch or only on all-success evidence. The first place mixed outcomes become an incorrect decision sets the triage boundary.
What to carry forward
Return the item outcome matrix, batch aggregation rule as observed, visible status, downstream gate, and first unsafe handoff. Keep a missing ledger event distinct from a recorded failure. The scope should identify aggregation, presentation, or downstream eligibility without asserting a cause prematurely.
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