{"version":"2.1.287","anchor":"comment-reply-retry-refused-when-session-network-access-is-o","canonical_anchor":"comment-reply-retry-refused-when-session-network-access-is-o","heading":"Claude stops retrying a comment reply when network access is off","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/comment-reply-retry-refused-when-session-network-access-is-o","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Claude stops retrying a comment reply when network access is off\n\nIf a comment reply fails and network access is off, Claude is told not to retry and to point you to the artifact's own page\n\n**Unclear.** It is not clear which tool shows this message or how often it is reached.\n\n**What**\n\nWhen Claude replies to a comment and the reply fails, Claude Code may try again. If that retry is refused because network access for the session is turned off or could not be confirmed, Claude now gets a specific message: the outcome is unknown, it should not retry, and it should tell you that you can reply on the artifact's own page. Before, there was only a general message saying the reply may have posted and to re-read the comments before retrying.\n\n**Why**\n\nThis stops Claude from posting the same comment twice when it cannot tell whether the first attempt got through.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5"}