{"version":"2.1.280","anchor":"remote-agent-session-polling-now-backs-off-and-fails-distinc","canonical_anchor":"remote-agent-session-polling-now-backs-off-and-fails-distinc","heading":"Cloud\/remote sessions get clearer, more specific failure reasons","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/remote-agent-session-polling-now-backs-off-and-fails-distinc","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Cloud\/remote sessions get clearer, more specific failure reasons\n\nCloud code review and remote-agent tasks now report more specific reasons when they fail, including a distinct session_not_found state\n\n**What**\n\n- The polling loop that checks on remote-agent tasks now counts repeated 404 (not-found) errors in a row, and once a review-mode task hits that threshold it can now fail with a new, distinct reason, `session_not_found`, instead of being lumped in with the existing `poll_timeout_after_api_error` reason.\n\n- Cloud\/async code review now also distinguishes and shows specific messages for two other failure states: the review session being archived before it finished, and the review being stopped remotely.\n\n**Why**\n\nInstead of a generic timeout or error message, users get a more accurate explanation when a cloud review or remote task fails, such as when a session can't be found (e.g. an account\/org mismatch) versus being archived or stopped, making it easier to understand what went wrong.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}