{"version":"2.1.257","anchor":"artifact-gateway-now-distinguishes-an-org-network-policy-ref","canonical_anchor":"artifact-gateway-now-distinguishes-an-org-network-policy-ref","heading":"Artifact gateway now distinguishes an org network-policy refusal from other relay failures","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/artifact-gateway-now-distinguishes-an-org-network-policy-ref","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### Artifact gateway now distinguishes an org network-policy refusal from other relay failures\n\nAn org network-policy refusal from the artifact gateway is now reported clearly instead of as a generic upstream failure.\n\nWhen the artifact\/session gateway responds with a 403 and a specific network-policy-denied body, the client now recognizes it as a distinct case rather than a generic upstream failure: telemetry records the `relay_policy_refused` outcome, the result carries `gatewayPolicy: \"network-off\"`, and the user sees a clearer message explaining that organization network policy denies artifact storage reads for this session.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}