Decide where the work belongs
Measure the recovery cost
Record the portion transferred, time to recreate the source, interruption point, and number of actions needed to recover. Note whether a full restart is merely slower or causes a different downstream artifact, and preserve the actual user choice.
Assess action confidence
For resume, restart, wait, and discard, write the evidence that would make the action safe. Mark which controls expose that evidence and whether a stale page or missing session could make the same control mean something else.
Choose an owner queue
Queue recovery contract work when the next action is undefined, transfer-state repair when a known session is mishandled, or status-copy work when behavior is safe but unexplained. Attach the interruption context and the state read used for the choice.
What to carry forward
Prioritize the issue when users can lose substantial transfer effort or create an ambiguous artifact by choosing among recovery actions without evidence. A clear restart after a documented nonresumable boundary should rank below a misleading resume control.
Technical background: tus protocol 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