{"version":"2.1.295","anchor":"retry-watchdog-skip-can-be-overridden-by-claude-code-retry-w","canonical_anchor":"retry-watchdog-skip-can-be-overridden-by-claude-code-retry-w","heading":"New CLAUDE_CODE_RETRY_WATCHDOG_MAX_WAIT_MS setting stops a retry check from being skipped","tier":"use","area":"API Retries","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/retry-watchdog-skip-can-be-overridden-by-claude-code-retry-w","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### New `CLAUDE_CODE_RETRY_WATCHDOG_MAX_WAIT_MS` setting stops a retry check from being skipped\n\nSetting `CLAUDE_CODE_RETRY_WATCHDOG_MAX_WAIT_MS` now stops Claude Code from skipping a check it otherwise skips because of the retry watchdog\n\n**Unclear.** Which feature this skip applies to is not stated, so the practical effect of setting the variable is unknown.\n\n**What**\n\nThere is a new environment variable, `CLAUDE_CODE_RETRY_WATCHDOG_MAX_WAIT_MS`. An environment variable is a named setting you give a program when you start it, for example in your shell.\n\nClaude Code has a check it skips when its retry watchdog (a timer that watches requests being tried again) is in use. That skip now only happens when `CLAUDE_CODE_RETRY_WATCHDOG_MAX_WAIT_MS` is not set. If you set it, the skip no longer happens.\n\n**Why**\n\nSetting this variable changes whether a feature runs that is otherwise skipped for some accounts and modes.\n\n- Area: API Retries\n- Names: `CLAUDE_CODE_RETRY_WATCHDOG_MAX_WAIT_MS`\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}