{"version":"2.1.280","anchor":"auto-mode-safety-check-failures-now-split-into-hard-vs-trans","canonical_anchor":"auto-mode-safety-check-failures-now-split-into-hard-vs-trans","heading":"Auto-mode safety-check failures now split into hard vs transient, with a retry cap","tier":"notice","area":"Auto Mode","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/auto-mode-safety-check-failures-now-split-into-hard-vs-trans","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Auto-mode safety-check failures now split into hard vs transient, with a retry cap\n\nClaude Code now tells apart hard vs transient safety-check failures in auto mode and caps retries\n\n**What**\n\nWhen Claude Code runs a safety check automatically and the check fails, it now sorts the failure into one of two kinds:\n\n- A hard failure, where retrying will not help, including two new causes: `server_call_unavailable_refused` and `server_call_unavailable_input_too_long`.\n\n- A transient failure, where the tool may retry once, waiting a bit longer each time it tries again.\n\nIf a transient failure keeps coming back with no verdict after repeated retries, the turn is stopped instead of retrying forever.\n\n**Why**\n\nThis keeps Claude Code from endlessly retrying a safety check that was never going to succeed, while still giving genuinely temporary failures a chance to clear up on their own.\n\n- Area: Auto Mode\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}