{"version":"2.1.304","anchor":"policy-limits-re-fetch-after-an-api-refusal-anthropic-api-k","canonical_anchor":"policy-limits-re-fetch-after-an-api-refusal-anthropic-api-k","heading":"Organisation policy limits are re-fetched as soon as the API refuses a request","tier":"notice","area":"Managed Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/policy-limits-re-fetch-after-an-api-refusal-anthropic-api-k","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Organisation policy limits are re-fetched as soon as the API refuses a request\n\nWhen the API refuses a request over an organisation policy the session has not loaded, Claude Code re-fetches its policy limits straight away\n\n**What**\n\nPolicy limits are rules your organisation sets for what Claude Code may do. When the API refuses a request because of an organisation policy the current session has not loaded yet, Claude Code now fetches the policy limits again right away and logs that it is re-fetching them.\n\nClaude Code also now watches whether use of `ANTHROPIC_API_KEY` has been approved, and reacts when that approval changes. It also records more reasons for a change in who is signed in, covering cases where a saved snapshot was used as a fallback or where stored data was restored.\n\n**Why**\n\nPolicy changes take effect sooner, instead of waiting for the regular hourly check.\n\n- Area: Managed Settings\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}