Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Cloud SessionsArea: what it touches
In DevelopmentKind: in v2.1.248,
In DevelopmentSection of the release
What
Cloud session startup failures now carry a reason and HTTP status, with a table saying which reasons are worth retrying. Epoch conflict, superseded by another worker, session not active and stale epoch are retryable; session not found, expired token and exhausted auth are not. A set of 401, 403, 404 and 429 sits alongside it. The error message itself already existed in the previous build, so what is new here is the classification table.
Evidence
superseded_by_worker
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
