Decide where the work belongs
Identify the next decision
Record what users do after cancelling: retry, remove, leave the page, or select another file. State how an incorrect assumption about the partial artifact could affect that choice, and note whether the workflow can safely be paused before the next action.
Map the state exposure
List the surfaces that show the file or session, including the upload list, detail view, retry control, and later processing status. Mark any surface that cannot distinguish partial, cancelled, complete, and discarded states.
Set a queue outcome
Queue lifecycle correction when stored state contradicts the cancellation contract, copy and control repair when behavior is correct but hidden, or race investigation when final responses can reverse the visible result. Include one cancellation trace with a known in-flight request.
What to carry forward
Prioritize the case when cancellation can cause a wrong retry, duplicate artifact, or false belief about discarded data. If the stored behavior is intentional and recoverable, queue state explanation first and preserve the exact post-cancel actions that need clarification.
Technical background: MDN reference.
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