Your production service receives HTTP 429 responses from the Claude API during traffic spikes. What is the BEST client behavior?
Select an answer to reveal the explanation.
Short Explanation and Infographic
When you hit 429, back off smartly — exponential delay + jitter — and push non-urgent work to queues or Batch API.
Full explanation below image
Full Explanation
Rate limits protect platform capacity. Correct handling: exponential backoff with jitter, honor Retry-After if present, reduce concurrency, and move bulk offline work to the Batches API. Tight loops worsen throttling. Removing auth fails and is insecure. Temperature does not control rate limits.