{"version":"2.1.225","anchor":"leaked-recovery-flag-detection-and-worker-credential-recover","canonical_anchor":"leaked-recovery-flag-detection-and-worker-credential-recover","heading":"Leaked recovery-flag detection and worker-credential recovery cap","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225\/e\/leaked-recovery-flag-detection-and-worker-credential-recover","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225","markdown":"### Leaked recovery-flag detection and worker-credential recovery cap\n\nRemote Control auth recovery stops looping forever when a credential keeps failing or a flag sticks.\n\n**What**\n\nTwo guards were added to Remote Control auth recovery so a stuck flag or a repeatedly failing credential no longer loops forever.\n\n**Details**\n\n- If the auth-recovery in-flight flag is still held past a computed ceiling, the close is handled directly and logged as leaked.\n- Close code 4094 gets its own attempt counter.\n- Recovery gives up after repeated failures with no successful heartbeat in between.\n\n**Evidence**\n\n`worker-credential recovery exhausted after `\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 0\/5"}