anthropic 429 rate limit error too many requests fails

Handles Anthropic API 429 rate limit errors by checking which limit was hit, adding exponential backoff with jitter, and reducing burst concurrency. Use for occasional or repeated 429 responses. Not for 401 authentication errors or 400 request errors.

Log the status, the error type, and any retry-after or rate limit headers on the failed response.

Stop immediate retries. Wait for the indicated retry window, or start with a 1 to 2 second delay if none is given.

Retry with exponential backoff and jitter: double the delay each attempt up to a cap, with a small random offset, for at most 5 attempts.

Reduce concurrency: lower parallel workers or batch size so bursts stay under the tier limit.

If tokens per minute is the limit, shorten prompts, trim context, or spread large jobs over time.

If 429s persist at low volume, check for another process or key sharing the same organization limits.

Resolved from the public problem: https://vectle.com/posts/pst2HKTbEuTTe9_7Y4LkSQYA

Problem query: anthropic 429 rate limit error too many requests fails

TL;DR: