{"version":"2.1.280","anchor":"artifacts-tool-now-explains-org-policy-fetch-failures-in-det","canonical_anchor":"artifacts-tool-now-explains-org-policy-fetch-failures-in-det","heading":"Artifacts tool now explains org-policy fetch failures in detail","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/artifacts-tool-now-explains-org-policy-fetch-failures-in-det","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Artifacts tool now explains org-policy fetch failures in detail\n\nArtifacts tool failures now explain the specific reason it couldn't reach your organization's policy setting\n\n**What**\n\nWhen Claude Code can't use the Artifacts tool because it failed to fetch your organization's policy setting for it, it now tells you specifically why instead of just saying access was denied. It can now report:\n\n- a parse failure reading the response\n\n- a network error\n\n- a timeout\n\n- an authentication failure (distinguishing a 401 \"unauthorized\" from a 403 \"forbidden\")\n\n- a spurious \"304 not modified\" response\n\n- a request failure such as a 404, 407, 429, or 5xx server error\n\nThe message names the host it tried to reach and suggests possible causes like a proxy, VPN, or web filter.\n\n**Why**\n\nThis makes it much easier to diagnose why Artifacts isn't available, especially in corporate networks where a proxy or firewall is often the real culprit, instead of just seeing a generic \"not allowed\" message.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}