{"version":"2.1.323","anchor":"resume-new-telemetry-and-refusal-path-for-interrupted-turns","canonical_anchor":"resume-new-telemetry-and-refusal-path-for-interrupted-turns","heading":"Resuming a turn that ended on an API error can now be held back","tier":"notice","area":"Resume","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/resume-new-telemetry-and-refusal-path-for-interrupted-turns","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Resuming a turn that ended on an API error can now be held back\n\nOn resume, Claude Code checks whether the cut-off turn ended on an API error and can decline to re-run it\n\n**Unclear.** Whether the switches that hold back these resumes are on or off by default is not stated.\n\n**What**\n\nWhen you resume a session, Claude Code now checks whether the last turn ended on an API error. A turn is one round of Claude working on your message, and an API error is a failure from Anthropic's servers. The errors it checks for are:\n\n- a rate limit\n\n- a model that could not be found\n\n- a server error\n\n- a missing request token\n\nIt records an event when this happens. A switch can stop Claude Code from resuming such a turn. A separate, remotely controlled switch makes Claude Code refuse to resume when a later command was already waiting in the queue. Before, this check was made only when the turn had been cut off while sending your prompt.\n\n**Why**\n\nThis changes whether a resumed session runs a failed turn again, which you will notice when you come back to it.\n\n- Area: Resume\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}