Decide where the work belongs
Separate false success from stale display
For each observed batch, write what the reader is likely to do from the screen and what the item ledger says instead. Rank a premature success or hidden failure above a visibly old timestamp. Keep a harmless refresh delay separate from a status that changes authorization.
Group evidence by batch shape
Compare fixed batches, filtered batches, empty selections, and batches with mixed outcomes. Record which shapes have an actual mismatch and which are only untested. One confirmed error in a common filtered workflow can outrank several isolated reports with no reproducible ledger.
Choose a bounded queue decision
Select immediate investigation, scheduled correction, or evidence collection. Name the next artifact required, such as a projection trace or denominator contract, and the event that raises priority. Do not use the visible count alone to estimate reach when item selection is unknown.
What to carry forward
Queue the work with a stated reader consequence, affected batch shape, confirmed evidence, and missing comparison. Escalate when progress can authorize a downstream action incorrectly. Otherwise schedule a narrow reporting investigation with a clear batch fixture and a review trigger for newly observed false terminal states.
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