{"version":"2.1.234","anchor":"artifact-comment-replies-no-longer-report-a-relay-failure-as","canonical_anchor":"artifact-comment-replies-no-longer-report-a-relay-failure-as","heading":"Artifact comment replies no longer report a relay failure as a clean failure","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/artifact-comment-replies-no-longer-report-a-relay-failure-as","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Artifact comment replies no longer report a relay failure as a clean failure\n\nComment replies that hit a bad relay now say the outcome is unknown instead of failed.\n\n**What**\n\nPosting a comment reply, resolving a thread and resolving a session now detect a response that did not come from the artifact service and return a `relay_error` outcome saying the result is unknown, instead of turning the HTTP status into a definite error.\n\n**Details**\n\n- The message tells Claude to re-read the comments before retrying, so a reply that did post is not duplicated.\n- This applies unconditionally on the relay path.\n\n**Evidence**\n\n`it may have posted; re-read the comments before retrying`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}