You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
ImprovementsKind: in v2.1.280,
ImprovementsSection of the release
What
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.
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.
Why
Instead 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.
