{"version":"2.1.219","anchor":"artifact-live-edit-no-longer-aborts-on-a-proxy-blocked-verif","canonical_anchor":"artifact-live-edit-no-longer-aborts-on-a-proxy-blocked-verif","heading":"Artifact live-edit no longer aborts on a proxy-blocked verification read","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219\/e\/artifact-live-edit-no-longer-aborts-on-a-proxy-blocked-verif","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219","markdown":"### Artifact live-edit no longer aborts on a proxy-blocked verification read\n\nLive editing artifacts works again behind egress proxies that block the artifact host.\n\n**What**\n\nIn environments whose egress proxy blocks the artifact host, live-edit failed on the pre-flight check instead of proceeding.\n\n**Details**\n\n- The pre-flight read that checks whether a live-edit target is a workshop page tags egress-proxy 403s with `deterministic: \"egress-blocked\"`\n- The live-edit guard throws its \"could not verify the target page is not a workshop page\" refusal only when the failure is not that tag\n\n**Evidence**\n\n`egress-blocked`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}