A blocked network request no longer looks like an artifact permissions problem.
What's wrong with this entry?
A 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.
- Failed responses now yield both a human-readable reason and a machine error
codetaken from the body'serrorfield, restricted to lowercase letters, digits and underscores, up to 64 characters.
sandbox proxy denied
Strings lifted out of the shipped bundle, so the claim above can be checked against them.