Establish what is happening
Capture file and connection conditions
Record file size, type, dimensions when relevant, local preparation time, device class, viewport, connection profile, and the exact upload action. Capture request start, progress events, bytes acknowledged, response arrival, and final state. Keep file contents out of the evidence unless they are explicitly safe.
Separate transfer from processing wait
Compare the last progress event with request completion and server acceptance or processing timestamps. A flat progress indicator can mean no bytes are moving or that the server is working after transfer. Align client and server identifiers, and mark any unobserved boundary as unknown.
Repeat with a smaller matched file
Use the same route, account state, device, and connection with a smaller file and then a file of similar type. Compare preparation, upload rate, pauses, retries, response size, and processing time. Note whether the stall appears at a size threshold, file type, or workflow step.
What to carry forward
Return a scope statement naming the file and network conditions, the last confirmed progress boundary, and the affected final state. Route the next work to preparation, transfer, server processing, or progress reporting. Stop when a smaller matched comparison rules in or out one boundary without inventing a cause.
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