{"version":"2.1.275","anchor":"new-artifact-egress-network-error-message-names-the-port-and","canonical_anchor":"new-artifact-egress-network-error-message-names-the-port-and","heading":"Artifact network and boot errors gain a transient flag and richer diagnostics","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/new-artifact-egress-network-error-message-names-the-port-and","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Artifact network and boot errors gain a transient flag and richer diagnostics\n\nArtifact tool network and boot failures now carry a transient flag plus more diagnostic detail like status, timing, and port requirements\n\n**What**\n\nError handling for the Artifact tool's network and boot requests was made more informative:\n\n- When an artifact content fetch fails with a plain network error, the message now explicitly states that outbound HTTPS on port 443 is required for the Artifact tool, instead of a generic \"network error\".\n\n- A new `transient` flag is now attached to some of these failures, marking them as potentially temporary.\n\n- Artifact publish\/boot-error telemetry now includes the original request, HTTP status, and sync\/agent\/relay context flags when the error is a boot request or failure.\n\n- Boot-request network failures are now also tagged with wall-clock timing (`wall_elapsed_ms`) and a relay flag, alongside the existing error code.\n\n**Why**\n\nThese changes make it easier to diagnose why an artifact failed to load or publish, and let callers distinguish transient (likely retryable) network problems from persistent ones.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}