Aglet

Verify cancellation before, after, and during job commit

Verification must make the commit race legible to both the job owner and its consumers. Run cancellation before the write, after the write, and with a deliberately delayed or incomplete readback. Confirm each path records what is known and prevents an ambiguous canceled label from authorizing unsafe work.

Check whether the outcome improved

  1. Verify cancel before commit

    Request cancellation while the job is paused before its durable write. Confirm no output or effect is committed, the worker reaches the documented canceled state, and a retry is allowed only under the stated rule. Read the records independently after the worker exits.

  2. Verify cancel after commit

    Request cancellation after the commit and compare the durable output, terminal state, acknowledgement, and dependent view. Confirm the committed result is represented and a retry does not repeat it without reconciliation. Preserve run and output identities in the verification record.

  3. Verify unknown readback

    Delay or withhold one commit readback and confirm the system uses an explicit review or unknown state. Check that operators cannot infer cancellation success from a request response. Restore the readback and verify reconciliation moves the job to the correct final state.

What to carry forward

Accept when pre-commit, post-commit, and unknown-readback cases have distinct, reconciled states and retry decisions. Reopen verification if cancellation can overwrite a commit, a downstream reader sees a false success or cancel, or unknown effects are silently treated as absent.

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