type URI on every rate_limit_exceeded problem body: https://docs.get-exo.com/errors/rate_limit_exceeded.
HTTP status: 429 Too Many Requests.
Why it happens
Limits are per credential and per family, so a burst of writes cannot drain your read allowance. The families are reads, writes, ingest, sessions, search and exports, each with its own burst capacity and sustained per-minute refill. The 429 response carries the sameRateLimit and RateLimit-Policy headers a successful response does, plus Retry-After in whole seconds.
How to fix it
- Honour
Retry-After. It is computed from your actual bucket state, not a fixed backoff. - Read
RateLimiton successful responses and slow down before you hit the wall:ris your remaining tokens andtis seconds until the bucket is full again. - Spread work over time rather than retrying immediately. Buckets refill continuously.
Related
too_many_streamsservice_degraded- Errors for the envelope and the full catalogue