Aglet

Verify upload recovery choices after connection interruptions

Verification should prove that connection loss produces a bounded, understandable recovery state across common interruption points. Test an active request, an acknowledged chunk, a final response gap, and a revisit. Confirm the displayed file identity, artifact state, and next action agree.

Check whether the outcome improved

  1. Exercise interruption paths

    Interrupt a multi-part transfer during a request, immediately after an acknowledgment, and just before completion. Reopen the workflow for one case. Record the state shown and expected choices before selecting any recovery action.

  2. Run each recovery choice

    Where offered, try resume, restart, wait, and discard against the same fixture. Verify each choice reaches its documented state, preserves or replaces the intended identity, and does not silently combine bytes from incompatible attempts.

  3. Inspect revisit behavior

    Leave and return after the interruption and after each choice. Confirm status, progress, controls, and any partial artifact remain consistent, and that a stale page cannot display a recovery action that no longer matches stored state.

What to carry forward

Accept recovery when each tested interruption has a documented state, an evidence-based next action, and a consistent result after revisit. Fail when a control hides uncertainty, creates a duplicate artifact, or reports resume or discard without corresponding state evidence.

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