Aglet

Prioritize post-commit cancellation by reconciliation risk

A cancellation after commit is dangerous when the visible state invites a retry without saying what was written. A clean canceled-before-commit result can be lower urgency. Prioritize ambiguous effects and any dependent action already taken, then the number of job types sharing the commit and cancellation path.

Decide where the work belongs

  1. Rank the unknown write

    For each race, list the records, output, messages, or external requests that could have committed after cancellation. Put an unknown non-idempotent effect ahead of a status-only discrepancy. Record whether a readback or reconciliation can establish the actual outcome.

  2. Compare boundary evidence

    Group occurrences by cancel-before-commit, cancel-after-commit, and missing commit record. Note whether the worker acknowledged the request before or after the write. A reproducible post-commit status overwrite is more actionable than a race with no correlated timestamps.

  3. Choose a safe queue action

    Select immediate reconciliation, a terminal-state contract review, or one controlled commit race. State what must be read before retry or cancel is repeated. Do not issue a second job while the original output and commit identity remain unknown.

What to carry forward

Queue the race with unknown effects, retry consequence, dependent action, and commit readback quality. Escalate when a canceled label can conceal durable work or authorize a duplicate. Otherwise schedule a controlled boundary investigation and keep unresolved outcomes in review.

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