{"version":"2.1.290","anchor":"output-filtered-api-stops-get-a-retry-budget","canonical_anchor":"output-filtered-api-stops-get-a-retry-budget","heading":"Filtered replies are retried when little or nothing had arrived","tier":"notice","area":"API Errors","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/output-filtered-api-stops-get-a-retry-budget","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Filtered replies are retried when little or nothing had arrived\n\nIf a reply is stopped by an output filter before much arrives, Claude Code now retries it up to a set number of times\n\n**Unclear.** The number of retries and where it is set are not stated.\n\n**What**\n\nA reply from the model can be stopped partway because its output was filtered. When that happens and nothing, or only the start of the reply, had arrived, Claude Code now retries the request up to a set number of times. Before, this kind of stop was not handled.\n\nA reply stopped as suspended, after only the model's thinking had arrived, is now treated the same as a lost connection or a cut-off reply.\n\n**Why**\n\nReplies stopped by a filter may now be retried automatically instead of simply failing.\n\n- Area: API Errors\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}