{"version":"2.1.269","anchor":"resume-suppression-logic-extended-to-trailing-api-error-turn","canonical_anchor":"interrupted-turn-resume-staleness-window-is-now-configurab","heading":"Interrupted-turn resume staleness window is now configurable, with wider coverage","tier":"use","area":"Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/resume-suppression-logic-extended-to-trailing-api-error-turn","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Interrupted-turn resume staleness window is now configurable, with wider coverage\n\nHow long an interrupted turn can be before Claude Code won't auto-resume it is now configurable, and the check now also covers trailing API-error turns\n\n**What**\n\n- The age cutoff that decides whether an interrupted turn is too old to auto-resume can now be set via the `CLAUDE_CODE_RESUME_INTERRUPTED_TURN_MAX_AGE_MS` environment variable or a new numeric flag, clamped between 60,000ms and 2,592,000,000ms (30 days). If neither is set, it defaults to 21,600,000ms (6 hours).\n\n- The same suppression logic now also applies to a trailing skipped turn that ended in an API error, not just an interrupted turn, checking its timestamp against the same age bound.\n\n- When resume is suppressed, Claude Code now logs more detail: the error kind, the age in minutes, where the bound came from, and the bound itself in minutes.\n\n**Why** This lets users and admins tune how long a stale, interrupted (or errored) turn is still eligible to resume automatically, and gives better diagnostics when a resume gets skipped.\n\n- Area: Sessions\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}