{"version":"2.1.246","anchor":"publish-over-an-existing-page-failures-now-distinguish-a-pro","canonical_anchor":"publish-over-an-existing-page-failures-now-distinguish-a-pro","heading":"Publish-over-an-existing-page failures now distinguish a proxy block from an HTTP error","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/publish-over-an-existing-page-failures-now-distinguish-a-pro","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Publish-over-an-existing-page failures now distinguish a proxy block from an HTTP error\n\nPublishing over an existing page now says whether a proxy block or an HTTP error stopped the check.\n\n**What**\n\nBefore overwriting a published page, Claude Code reads it to confirm it is not a certified review page. If that read is blocked by the sandbox proxy, the failure message now says whether retrying is worth it.\n\n**Details**\n\n- A transient content-scan denial advises reading the page again or publishing fresh.\n- Any other proxy denial drops retry advice entirely and says \"Publish a fresh artifact instead (omit `url` and use a new `file_path`).\"\n- The older HTTP 403 and generic-status wording is now used only for failures that were not proxy denials.\n- Unconditional on the publish-overwrite verification path.\n\n**Evidence**\n\n`content_scan_transient`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}