Decide where the work belongs
Name the mistaken action
Record whether people cancel, reload, retry, or wait unnecessarily when progress stops. Tie the action to the file size, transfer phase, and visible message, and distinguish wasted effort from a risk of creating a second artifact.
Map affected phases
List the stages and file classes where the display stalls: large ranges, finalization, validation handoff, or slow acknowledgments. Mark whether the underlying transfer continues and whether a separate status cue explains the next phase.
Select the queue
Queue event or denominator repair when measured progress is wrong, state-copy repair when transfer is healthy but phase language is absent, or transport investigation when bytes also stop. Attach paired visible and receiver observations.
What to carry forward
Prioritize the issue when the display causes a foreseeable cancellation, duplicate retry, or false completion. Lower urgency is appropriate for a cosmetic pause that remains explicitly labeled, explains the current phase, and leaves the next action unambiguous.
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