{"version":"2.1.247","anchor":"comment-reads-that-the-session-cannot-carry-get-their-own-er","canonical_anchor":"comment-reads-that-the-session-cannot-carry-get-their-own-er","heading":"Comment reads that the session cannot carry get their own error","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/comment-reads-that-the-session-cannot-carry-get-their-own-er","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Comment reads that the session cannot carry get their own error\n\nA comment read your session can't carry now returns a distinct retry-once error instead of a generic failure.\n\n**What**\n\nWhen the session's connection does not serve a comment read, the result is now a distinct error telling the model to retry once and otherwise tell you comments cannot be read from this session right now, instead of a generic failure.\n\n**Details**\n\n- Telemetry records `server_read_relay_unavailable` along with the HTTP status.\n\n**Evidence**\n\n`server_read_relay_unavailable`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}