{"version":"2.1.248","anchor":"managed-settings-fetch-failures-now-say-why-and-that-proxy-e","canonical_anchor":"managed-settings-fetch-failures-now-say-why-and-that-proxy-e","heading":"Managed-settings fetch failures now say why, and that proxy env is withheld","tier":"notice","area":"Managed Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/managed-settings-fetch-failures-now-say-why-and-that-proxy-e","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Managed-settings fetch failures now say why, and that proxy env is withheld\n\nManaged settings failures now name the reason and warn that proxy settings aren't applied.\n\n**What**\n\nWhen Claude Code cannot fetch your organization's managed settings, the message now names the reason (401\/403, other 4xx\/5xx, timeout, network, parse error, invalid settings, or a gateway-pin mismatch). If it falls back to a cached copy, it also tells you that transport environment settings from that policy are not applied.\n\n**Details**\n\n- On a stale cache, proxy, CA certificate and provider environment values from managed policy are withheld until a fetch succeeds; the rest of the cached settings still apply.\n\n**Evidence**\n\n`; proxy\/CA\/provider env withheld until a fetch succeeds`\n\n- Area: Managed Settings\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}