{"version":"2.1.246","anchor":"blocked-artifact-content-fetches-say-whether-the-block-is-te","canonical_anchor":"blocked-artifact-content-fetches-say-whether-the-block-is-te","heading":"Blocked artifact content fetches say whether the block is temporary","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/blocked-artifact-content-fetches-say-whether-the-block-is-te","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Blocked artifact content fetches say whether the block is temporary\n\nA proxy-blocked artifact fetch now says whether it's a temporary scan outage or a permanent block.\n\n**What**\n\nWhen the sandbox proxy blocks a fetch of artifact content with HTTP 403, the failure is now sorted into a temporary scan outage versus a permanent block, each with its own explanation, so the model knows whether to retry.\n\n**Details**\n\n- A 403 whose reason ends in \"(fail closed)\" is treated as transient; other content-scan blocks are treated as permanent.\n- A separate message covers proxy denials that are not content-scan related.\n\n**Evidence**\n\n`artifact content fetch blocked: the sandbox proxy's content scan was unavailable (HTTP 403). This is transient; retry.`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}