Appearance
rate_limited
Rate limited · HTTP 429
Over the limit. On the control API, per credential and per operation's bucket, and the RateLimit-* and Retry-After headers say when to try again. On a client, the connection sent requests faster than the server serves them.
What to do: On the control API, wait as long as Retry-After says, then retry. A burst that hits this regularly needs batching, not retries.
Where it comes from:
- Control API
- Signaling — a client's connect, a request, or an event
Branch on code; detail is for your logs and never for a user. All error codes.