Incident Dossier
A Retry-After That Returns Too Soon
A mailbox-reading integration receives a temporary throttle response with a wait instruction. It retries several times almost immediately and never reaches the fixture's recovery window. Normal reads succeed. Investigate the timing contract between the response parser, retry policy and scheduler. This is original Buglyst simulation code, not Microsoft's implementation, a reconstruction of a Microsoft outage, or a claim about an incident's root cause. All clocks and transport responses are deterministic and local.
Initial failing signalThe read remains throttled after all allowed attemptsExpected behavior: The second read begins after the advertised two-second cooldown and returns 200. · actual behavior: Three reads occur within four milliseconds, ending with 429.