{"version":"2.1.246","anchor":"republishing-a-pr-review-reports-a-denied-read-separately-fr","canonical_anchor":"republishing-a-pr-review-reports-a-denied-read-separately-fr","heading":"Republishing a PR review reports a denied read separately from a failed one","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/republishing-a-pr-review-reports-a-denied-read-separately-fr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Republishing a PR review reports a denied read separately from a failed one\n\nRepublishing a PR review distinguishes a proxy-denied read from an HTTP failure.\n\n**What**\n\nBefore republishing a review, Claude Code re-reads the published page to check where the decision came from. A read blocked by the proxy now produces a short \"read denied\" message instead of the retry guidance meant for HTTP failures.\n\n**Details**\n\n- The read result carries a new denial field that did not exist in 2.1.245.\n- The \"retry at most once\" and \"HTTP failure is not transient\" wording is kept for 403 and other HTTP statuses.\n\n**Evidence**\n\n`proxyDeny`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}