When 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.
Artifact gateway now distinguishes an org network-policy refusal from other relay failures
An org network-policy refusal from the artifact gateway is now reported clearly instead of as a generic upstream failure.
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
ImprovementsKind: in v2.1.257,
ImprovementsSection of the release