A third of partner API calls are answered with HTTP 429 while the agreed rate-limit hotfix waits to deploy.
A partner's batch job started at 10:00 and the gateway has been answering a third of its calls with HTTP 429 since.
The deploy pipeline only builds what is on origin/main, and your push came back rejected.
Someone suggests forcing it through.
Before anything goes to origin, find out what origin has that you do not.
The fix is yours to find: hints, the recovery checks and the debrief unlock inside the incident.
The alert fires and the clock starts. Read the page and the briefing.
Work in a simulated shell with realistic output: logs, configs, services.
Change the system the way you would in production. Hints are there if you get stuck.
Automated checks verify the recovery, then the debrief explains what happened.
Free, instant, and it works on your phone. No signup: start as a guest and save your progress later.