{"version":"2.1.224","anchor":"remote-bridge-retries-once-after-refreshing-an-expired-token","canonical_anchor":"remote-bridge-retries-once-after-refreshing-an-expired-token","heading":"Remote bridge retries once after refreshing an expired token","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/remote-bridge-retries-once-after-refreshing-an-expired-token","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Remote bridge retries once after refreshing an expired token\n\nA remote bridge session that hits an expired token now refreshes and retries once.\n\n**What**\n\nA remote bridge session that gets a 401 during startup now refreshes the OAuth token and tries again, instead of failing. The refresh runs at most once per access token, and if it lands on the final attempt an extra call is made with the fresh token.\n\n**Details**\n\n- Reports `bridge_repl_v2_init_401_refresh` with a flag saying whether a token was actually refreshed or no refresh was available.\n- Disconnect reasons \"untrusted_device\" and \"session_stale_relogin\" are now classified as auth problems rather than terminal failures, so they take the recoverable path.\n\n**Evidence**\n\n`bridge_repl_v2_init_401_refresh`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}