Build a useful investigation brief
Prepare loss timing cases
Use one multi-part file and interrupt it during an active request, after an acknowledged range, and before a response. Repeat once with the page open and once after reopening, recording local state and expected recovery evidence for each path.
Trace state reads and writes
List connection events, request responses, session persistence, object records, page initialization, and control changes in order. Mark missing transitions and any point where the file identity or checkpoint is replaced without a documented reason.
Compare recommended actions
For each path, compare the offered resume, restart, wait, or discard action with receiver evidence. Identify the earliest mismatch between proven state and recommendation, leaving a timing race as a hypothesis until event ordering supports it.
What to carry forward
The investigation is sufficient when a controlled loss path explains why the interface recommends a specific recovery action and how the stored state supports it. If the session is not observable, document the decision gap and avoid claiming that resume or discard is safe.
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