You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Cloud SessionsArea: what it touches
ImprovementsKind: in v2.1.232,
ImprovementsSection of the release
What
When a cloud worker connection is rejected as conflicting, the reason is now more specific: a session that is archived or no longer active, or one superseded by a newer worker, are reported separately from a stale epoch.
Details
superseded_by_worker and session_not_active join epoch_stale and epoch_conflict, all closing with code 4090.
Diagnostics read "session archived or no longer active" and "superseded by a newer worker".
The session-not-active case emits its own telemetry event.
Evidence
cli_worker_session_not_active
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
