{"version":"2.1.312","anchor":"org-settings-load-errors-name-the-retry-state","canonical_anchor":"org-settings-load-errors-name-the-retry-state","heading":"Organization settings errors no longer always say they are retrying","tier":"notice","area":"Managed Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/org-settings-load-errors-name-the-retry-state","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Organization settings errors no longer always say they are retrying\n\nWhen organization-managed settings fail to load, the error no longer always says \"Retrying\" and instead reflects what Claude Code will do\n\n**What**\n\nWhen settings managed by your organization fail to load, the error message used to always say \"Retrying;\". That part of the message now changes with the situation, and it still ends with \"check [https:\/\/status.anthropic.com](https:\/\/status.anthropic.com) if this persists.\"\n\n**Why**\n\nThe message no longer claims a retry is happening when none is.\n\n- Area: Managed Settings\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: org\n- Heads-up: no"}