What this tests

authretry-logic

Point your client at this specimen and find out — before prod does — whether it handles auth failure without panic-retrying into a second incident.

Anatomy

OAuth tokens expire mid-session like milk with ambitions. Your batch job has been happily authenticated for two hours, then — 401, invalid_token, you're nobody now. The API forgets you the way a nightclub bouncer forgets you the instant you step outside for air: no grudge, no ceremony, just a door that used to be open. The correct response is refresh-then-retry-once. The incorrect response, beloved of a thousand codebases and at least one bank, is retrying the dead token in a tight loop until the rate limiter loses patience and adds insult to authentication failure — at which point you get to enjoy BOTH specimens. Watch your client either do the right thing or spend eternity knocking on a door that will never open again. Both outcomes are educational. Only one of them is billable.

Source: Microsoft identity platform — access token lifetime

Replay it

curl -i https://faultydata.com/r/FD-2026-005

// response appears here

Signature

{Status:401 Headers:map[WWW-Authenticate:Bearer error="invalid_token", error_description="The access token expired"] Body:{"error":{"code":"InvalidAuthenticationToken","message":"Access token has expired or is not yet valid."}} Corrupt: Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[]}

Keep digging

FD-2026-027 — Signing-key rollover breaks token validation (Azure AD, Mar 2021) FD-2026-026 — Global authentication outage (Google, Dec 2020) FD-2026-001 — Stripe-style rate limit FD-2026-004 — GitHub secondary rate limit FD-2026-009 — Provider overloaded (OpenAI-style 529) FD-2026-032 — Capacity-collapse 503s (Healthcare.gov launch, Oct 2013)