{"version":"2.1.232","anchor":"worker-disconnects-say-which-conflict-happened","canonical_anchor":"worker-disconnects-say-which-conflict-happened","heading":"Worker disconnects say which conflict happened","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/worker-disconnects-say-which-conflict-happened","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Worker disconnects say which conflict happened\n\nCloud worker rejections now name the specific conflict: archived, superseded or stale epoch.\n\n**What**\n\nWhen 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.\n\n**Details**\n\n- `superseded_by_worker` and `session_not_active` join `epoch_stale` and `epoch_conflict`, all closing with code 4090.\n- Diagnostics read \"session archived or no longer active\" and \"superseded by a newer worker\".\n- The session-not-active case emits its own telemetry event.\n\n**Evidence**\n\n`cli_worker_session_not_active`\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}