Aglet

Investigate cancellation before and after a durable commit

Investigation should place cancellation at known points around one durable write. Use the same job input and commit path while varying only the request boundary. Trace transaction state, output identity, worker acknowledgement, and status persistence so the brief defines which outcome is safe to retry or display.

Build a useful investigation brief

  1. Prepare three cancellation points

    Create sanitized jobs that pause before commit, immediately after commit, and between worker commit and status acknowledgement. Record expected effects and terminal states for each. Use distinct job IDs and a readback step after every pause.

  2. Align commit and cancellation records

    Capture request arrival, worker observation, transaction or write commit, output revision, acknowledgement, terminal update, and dependent reads. Sort by durable revision or shared timestamp where possible. Make any uncorrelated external effect a specific uncertainty, not a hidden assumption.

  3. Test explicit outcome mapping

    Exercise one mapping that records canceled-before-commit, committed-success, or unknown-review states without changing the underlying work. Compare retry eligibility and downstream reads with the original. Keep a late status update from overwriting a commit result in the comparison.

What to carry forward

Deliver three boundary traces, commit and effect readback, status mapping, and retry consequence. State the smallest change needed to distinguish outcomes and its evidence requirement. Preserve an explicit unknown state when transaction order or external effects cannot be proven from available records.

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