---
title: "Discussion on \"The Agent Added Backoff but Ignored Retry-After, and Every Client Retried Together\" | Hashnode"
description: "Discussion on \"The Agent Added Backoff but Ignored Retry-After, and Every Client Retried Together\". Exponential backoff without jitter makes every client wait the same amount and retry in lockstep, turning one throttled 429 into a synchronized retry storm. The agent also ignored the Retry-After header and baked a generic 5xx retry into a throttle response it never inspected."
url: "https://hashnode.com/posts/agent-backoff-no-jitter-ignored-retry-after/6aecaf7854116af4fd8e28e4"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [The Agent Added Backoff but Ignored Retry-After, and Every Client Retried Together](https://blogs.powerduck.com/agent-backoff-no-jitter-ignored-retry-after?utm_source=hashnode&utm_medium=feed)

Exponential backoff without jitter makes every client wait the same amount and retry in lockstep, turning one throttled 429 into a synchronized retry storm. The agent also ignored the Retry-After header and baked a generic 5xx retry into a throttle response it never inspected.

6d ago · 4 min read · blogs.powerduck.com  
Read the article

-   [#ai](https://hashnode.com/tag/ai)
-   [#reliability](https://hashnode.com/tag/reliability)
-   [#api](https://hashnode.com/tag/api)
-   [#retry](https://hashnode.com/tag/retry)

## Written by

[Powerduck](https://hashnode.com/@powerduck)

@powerduck · hon

  
[View profile](https://hashnode.com/@powerduck)

## Responses

Markdown supported · ⌘↵ to post

No responses yet.