Establish what is happening
Capture request and deadline context
Record route, method, input shape, client deadline, server deadline, request identifier, start time, response or timeout moment, device or network context, and the user action waiting. Redact sensitive values. Include whether the caller retried and what visible state followed.
Align work with timeout moments
Compare admission, handler, query, lock, dependency, serialization, transfer, client timeout, and durable commit timestamps where available. Identify the first deadline crossed and whether processing continued afterward. Mark an unknown commit boundary explicitly because timeout and failure are different outcomes.
Compare a near-timeout success
Replay the same route, input structure, account or dataset class, and dependency conditions with a request that completed just inside its deadline. Compare query shape, result size, resource waits, response behavior, and final state. Preserve the timing difference without treating it as a proven cause.
What to carry forward
Return a scope statement naming the deadline boundary, affected action, near-timeout match, final-state evidence, and uncertainty about completion. Route next work to client, server, data, dependency, or retry ownership. Stop when one controlled request can distinguish waiting from abandoned work.
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