{"version":"2.1.225","anchor":"bridge-recovery-for-expired-worker-credentials-on-close-code","canonical_anchor":"bridge-recovery-for-expired-worker-credentials-on-close-code","heading":"Bridge recovery for expired worker credentials on close code 4094","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225\/e\/bridge-recovery-for-expired-worker-credentials-on-close-code","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225","markdown":"### Bridge recovery for expired worker credentials on close code 4094\n\nWhen your remote worker credential expires, the bridge now re-mints it and refreshes login instead of dying.\n\n**What**\n\nThe remote bridge can now recover from a worker credential expiry instead of just reporting the close code, re-minting the credential and forcing an OAuth refresh.\n\n**Details**\n\n- Adds a recovery-table entry for close code 4094 alongside the existing 401, 4091 and 4093 entries.\n- The 4094 entry re-mints the worker credential and sets `needsOAuthRefresh: !0`.\n- Epoch-mismatch conditions `token_expired` and `auth_exhausted` map to 4094.\n- Gated on the typed close-code mapping, passed as `causeTypedCloseCodes: !0` by both bridge callers, so it is active for the remote bridge.\n- The plain \"code 4094\" close-reason text existed in 2.1.224; only the recovery handling is new.\n\n**Evidence**\n\n`worker credential expired \\u2014 re-minting`\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}