Aglet

Verify batch progress across filtered and active items

Verification must show that the progress view tells the same story as its item ledger across the batch shapes that exposed the problem. Exercise all-success work, filtered records, a mixed terminal set, and an item still running. Read the persisted result after each transition rather than trusting a single refreshed screen.

Check whether the outcome improved

  1. Check selection and denominator fixtures

    Run a batch with every selected item eligible, then repeat with a filter that excludes known records. Compare the displayed denominator with the recorded selection and confirm excluded items are labeled or omitted consistently. Save the input and expected counts for each run.

  2. Check mixed and active outcomes

    Leave one item active while others complete and fail, then finish it and reread the projection. Confirm active work is not counted as complete and failed work remains visible for review. Include an item whose update arrives after the initial page load.

  3. Check refresh and terminal wording

    Reload from a separate session or fresh request after each transition. Compare the last-update time, status wording, and item counts with durable records. Verify that a fully terminal batch cannot retain an earlier active label or suggest success when failures remain.

What to carry forward

Accept the change when every fixture has matching selection, denominator, item outcomes, projection age, and terminal wording. Record any unsupported state explicitly. If a count matches only after manual refresh, keep verification open until the read freshness contract is addressed.

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