Establish what is happening
Capture the rejected request context
Record route, method, actor or credential class, resource key, request time, response status, response metadata, request volume, concurrency, client workflow, and whether a retry followed. Redact credentials and sensitive values. Note which critical action was blocked and how the interface described the limit.
Compare allowed and rejected requests
Use requests with the same route and actor scope just inside and outside the observed limit. Compare count, window or reset evidence, payload, concurrency, shared resource, response status, and other work occurring at the time. Mark undocumented policy behavior as uncertain.
Check reset and retry behavior
Observe a request before, during, and after the reported reset boundary in a controlled environment. Record client retry timing, repeated responses, successful recovery, and duplicate actions. Distinguish a limit response from a server error or timeout so handling remains contract-specific.
What to carry forward
Return a scope statement naming actor and resource scope, observed boundary, blocked action, reset evidence, retry behavior, and uncertainty. Route next work to policy calculation, scope, capacity, client handling, or documentation. Stop when one controlled comparison can test the limit's actual ownership.
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