When a tool call fails because of a network timeout or rate limit, retrying immediately may add to the problem. Exponential backoff schedules retries with increasing waits between attempts. Add jitter—a little randomized variation—so failed agents do not all retry at the same instant. section 2.4.1 section 4.4.3
Place backoff inside a broader failure-handling plan:
- Retry transient failures, but set a retry limit and surface a clear error when attempts are exhausted. section 4.1.3 section 4.4.3
- Use structured errors, fallback paths, and timeouts where appropriate; backoff alone cannot fix every failed or hanging tool. section 2.4.1
A failed pipeline stage
If an agent stage hits a rate limit, wait before trying that stage again rather than restarting immediately. Increase the wait on later attempts, vary it with jitter, and report an error if the retry budget runs out. Retries cost time and tokens, so reserve them for failures they may resolve. section 4.1.3 section 4.4.3







