Aglet

Triage an upload after network loss leaves recovery unclear

After connectivity drops, an upload may still have a valid session, an incomplete request, or no recoverable state. Triage should capture what the interface says, what the receiver knows, and which actions are offered. The key question is whether each suggested action matches proven state.

Establish what is happening

  1. Freeze the interruption context

    Record file identity, bytes or chunk acknowledged, active request, connection event, and visible control state when the loss occurred. Note whether the page remained open, was reloaded, or was revisited before the recovery choice appeared.

  2. Inspect recoverable state

    Check for an upload session, partial object, terminal response, or absent record. Compare any stored checkpoint with the local file and determine whether a resume request could identify the same source without guessing at its contents.

  3. Classify the decision gap

    Classify the case as missing status, unsafe resume, unnecessary restart, unclear discard, or delayed reconnection. State the evidence needed for each action and keep uncertainty visible when the receiver cannot confirm its state.

What to carry forward

Triage is complete when the interruption, recoverable artifact, and offered next actions are recorded for one file. If no state evidence distinguishes resume from restart, classify the ambiguity itself as the defect and do not infer safety from a button label.

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