{"version":"2.1.246","anchor":"artifact-request-failures-say-when-the-sandbox-proxy-blocked","canonical_anchor":"artifact-request-failures-say-when-the-sandbox-proxy-blocked","heading":"Artifact request failures say when the sandbox proxy blocked them","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/artifact-request-failures-say-when-the-sandbox-proxy-blocked","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Artifact request failures say when the sandbox proxy blocked them\n\nA blocked network request no longer looks like an artifact permissions problem.\n\n**What**\n\nA 403 from the sandbox proxy is now recognised and logged separately from a denial by the artifact service itself, so a blocked network egress no longer looks like a permissions problem with the artifact.\n\n**Details**\n\n- Failed responses now yield both a human-readable reason and a machine error `code` taken from the body's `error` field, restricted to lowercase letters, digits and underscores, up to 64 characters.\n\n**Evidence**\n\n`sandbox proxy denied`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}