Decide where the work belongs
Rank the workflow blocked by upload
Name the action that cannot proceed until the file is accepted, such as attaching evidence or completing a handoff. Separate a delayed preview from a blocked save. Give weight to uploads that occur at a deadline or are repeated across a workflow because the wait compounds.
Group reach by file and network shape
Classify observations by file size, type, preparation time, device, connection, account state, and whether a retry succeeds. Mark confirmed frequency separately from untested limits. A stall across ordinary files supports urgent work, while a narrow boundary may need a focused reproduction first.
Choose a bounded queue outcome
Select investigate now, schedule a transfer or feedback improvement, or collect one missing file and connection comparison. State the evidence that would change priority, such as a repeatable size threshold or processing wait. Keep a future resumability design separate from the immediate evidence slice.
What to carry forward
Produce a queue decision tied to blocked work, confirmed file-shape reach, and recovery quality. Include whether the stall is new, growing, or longstanding. The result is actionable when the next engineer has one representative upload to reproduce and knows why it deserves capacity.
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