{"version":"2.1.281","anchor":"remote-managed-settings-fetch-stops-retrying-on-non-retryabl","canonical_anchor":"remote-managed-settings-fetch-stops-retrying-on-non-retryabl","heading":"Remote managed-settings fetch stops retrying on non-retryable 4xx","tier":"notice","area":"Managed Settings","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/remote-managed-settings-fetch-stops-retrying-on-non-retryabl","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Remote managed-settings fetch stops retrying on non-retryable 4xx\n\nFetching remote managed settings no longer retries on most 4xx errors, only on 408, 409 and 429\n\n**What**\n\nManaged settings are settings that an organisation delivers to Claude Code from a server. When fetching them fails with a 4xx status, which is a kind of error the server returns about the request itself, Claude Code now stops retrying. The exceptions are these statuses, which are still retried:\n\n- 408\n\n- 409\n\n- 429\n\nBefore, only 401 and 403 errors, the ones about sign-in and permission, skipped the retry. The failure result now also includes more detail about the error.\n\n**Why**\n\nA request the server has already rejected will not succeed if repeated. Claude Code now gives up on those instead of trying again.\n\n- Area: Managed Settings\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}