{"version":"2.1.225","anchor":"remote-control-bridge-token-refresh-exhaustion-now-surfaces-","canonical_anchor":"remote-control-bridge-token-refresh-exhaustion-now-surfaces-","heading":"Remote Control bridge: token-refresh exhaustion now surfaces a login prompt","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225\/e\/remote-control-bridge-token-refresh-exhaustion-now-surfaces-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225","markdown":"### Remote Control bridge: token-refresh exhaustion now surfaces a login prompt\n\nWhen remote control can't refresh your token, it now tells you to run \/login instead of stalling.\n\n**What**\n\nWhen the bridge runs out of token-refresh retries, the session is marked failed with an instruction to run \/login instead of stalling silently.\n\n**Details**\n\n- The refresher gained an `onExhausted` callback fired after the configured number of consecutive failures, logged at error level\n- Existing \"Refresh chain exhausted for sessionId=\" logging and `bridge_token_refresh_exhausted` telemetry are unchanged\n- The bridge supplies the callback and moves the session into a failed\/auth state carrying the user-facing reason\n- Token-refresh failures inside `getAccessToken` are now caught and logged rather than thrown\n- A new `cred_4094_recovery` cause joins the recovery connect-timeout classification\n\n**Evidence**\n\n`OAuth token unavailable \\u2014 run \/login to restore Remote Control`, `run \/login to restore Remote Control`\n\n- Area: Remote Control\n- Names: `\/login`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}