Build a useful investigation brief
Prepare three controlled stop points
Create a sanitized batch with an item that can pause before work, after its checkpoint, and inside a bounded blocking call. Record the expected effects for each pause. Use fresh batch IDs so a previous cancellation acknowledgement cannot affect the next run.
Follow signal to durable state
Capture the request, worker observation, checkpoint write, item terminal state, and side-effect records in order. Note whether the worker exits, finishes the current safe action, or reaches another effect. A missing event is evidence to resolve, not permission to infer a stop.
Test a cooperative check
Add or exercise one cancellation check at the next safe boundary in the controlled fixture, without changing unrelated work. Compare the last possible effect and terminal status with the original trace. If a blocking call still runs, document that limit and its recovery behavior.
What to carry forward
Deliver a cancellation brief with three stop points, observed signal timing, last permitted effect, and terminal-state mapping. Identify the smallest safe checkpoint for a change and the limits of interrupting an in-flight call. Do not call the investigation complete while post-acknowledgement effects remain unexplained.
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