{"version":"2.1.225","anchor":"bridge-reconnects-only-refresh-oauth-for-the-close-codes-tha","canonical_anchor":"bridge-reconnects-only-refresh-oauth-for-the-close-codes-tha","heading":"Bridge reconnects only refresh OAuth for the close codes that need it","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225\/e\/bridge-reconnects-only-refresh-oauth-for-the-close-codes-tha","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225","markdown":"### Bridge reconnects only refresh OAuth for the close codes that need it\n\nRemote Control reconnects skip needless token refreshes, so ordinary disconnects recover faster.\n\n**What**\n\nReconnect recovery no longer forces an OAuth refresh for every handled close code, cutting unnecessary token work on non-auth disconnects.\n\n**Details**\n\n- The per-close-code recovery table (401, 4091, 4093, 4094) gains `needsOAuthRefresh`, true for 401 and 4094 only.\n- The flag decides whether to force an OAuth refresh up front, whether to enter the retry loop that prompts for a fresh login, and whether to do a late refresh instead.\n- The CCR client gained an `onRequestAuthOk` callback fired on a successful heartbeat, wired through the bridge so the session can mark auth as proven.\n\n**Evidence**\n\n`needsOAuthRefresh`\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 0\/5"}