{"version":"2.1.292","anchor":"remote-settings-fetch-abortable-with-a-shared-401-recovery","canonical_anchor":"remote-settings-fetch-abortable-with-a-shared-401-recovery","heading":"Managed settings fetch can be cancelled and refreshes login only once after a 401","tier":"internal","area":"Managed Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/remote-settings-fetch-abortable-with-a-shared-401-recovery","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Managed settings fetch can be cancelled and refreshes login only once after a 401\n\nFetching remote managed settings can now be cancelled, and after a 401 error Claude Code forces a login token refresh only once\n\n**What**\n\nClaude Code fetches remote managed settings (settings an organisation sets centrally). That fetch has changed in a few ways:\n\n- It can now be cancelled.\n\n- After a 401 error (the server rejecting the login), Claude Code forces a refresh of the login token only once across all retries. Before, it forced a refresh on each 401 whenever a token existed and the call was not already a retry.\n\n- If the fetch has already been cancelled, a 401 is returned as is without a refresh.\n\n- The result of the last forced refresh is kept on the final result.\n\nThe fetch for policy limits can also be cancelled now, and keeps its own count of recovery attempts that resets on each retry.\n\n**Why**\n\nThis should stop runs of repeated token refreshes, and lets a cancelled session stop waiting for these fetches.\n\n- Area: Managed Settings\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}