An artifact fetch blocked by your corporate proxy now says so instead of looking like a service failure.
What's wrong with this entry?
An artifact content fetch blocked by a corporate egress proxy now reports its own reason code and an error naming the proxy's CONNECT status, rather than a generic relay failure, so a network policy problem is distinguishable from a service problem.
- A separate message explains that asset reads work only locally or from a cloud session with the gateway relay enabled.
artifact content fetch refused by the environment's egress proxy
Strings lifted out of the shipped bundle, so the claim above can be checked against them.