Aglet

Triage an upload cancellation with an unclear artifact state

Cancellation can stop bytes while leaving a resumable object, remove the object while the interface still lists it, or race with a final response. Triage should capture the action timing and resulting states at both client and storage boundaries, then state what artifact behavior the workflow promises.

Establish what is happening

  1. Capture the cancellation point

    Record the file identity, bytes sent, visible progress, active request, and exact user action when cancellation occurred. Note whether the interface showed cancelling, cancelled, failed, or complete, and preserve any response that arrived afterward.

  2. Inspect artifact states

    Check whether a partial object, upload session, completed document, or temporary record remains and how each is linked to the file identity. Distinguish an intentionally resumable artifact from leftover state that the user cannot discover or control.

  3. Name the expectation

    Write the expected post-cancel behavior: stop and retain, stop and discard, or finish the in-flight operation. Classify the case as state mismatch, race handling, or missing explanation when the product contract does not select one.

What to carry forward

Triage is complete when the cancel timing, visible state, and stored artifact state are recorded against one file identity. If the workflow has no stated retention choice, treat the missing cancellation contract as the primary finding.

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