{"version":"2.1.224","anchor":"worker-shutdowns-carry-a-typed-reason","canonical_anchor":"worker-shutdowns-carry-a-typed-reason","heading":"Worker shutdowns carry a typed reason","tier":"internal","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/worker-shutdowns-carry-a-typed-reason","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Worker shutdowns carry a typed reason\n\nBackground worker exits now carry a typed reason such as expired token or epoch conflict.\n\n**What**\n\nFatal exits now pass a reason such as session not found, token expired, auth exhausted, or an epoch conflict or stale epoch, instead of terminating with no explanation.\n\n**Details**\n\n- The remote bridge maps auth-related reasons to WebSocket close code 4094 and the rest to 4090, so recovery can pick the right path.\n\n**Evidence**\n\n`causeTypedCloseCodes`\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}