{"version":"2.1.238","anchor":"three-new-remote-bridge-flags-for-auth-recovery-and-session-","canonical_anchor":"three-new-remote-bridge-flags-for-auth-recovery-and-session-","heading":"Three new remote bridge flags for auth recovery and session end","tier":"internal","area":"Remote Bridge","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/three-new-remote-bridge-flags-for-auth-recovery-and-session-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Three new remote bridge flags for auth recovery and session end\n\nThree new remote-bridge switches appear, covering a retry after a rejected token refresh and two unread ones.\n\n**What**\n\nThree new remote-bridge feature checks appear, all defaulting to on when the server says nothing. `tengu_dazzling_garden` guards a second OAuth recovery attempt after a forced token refresh is rejected. `tengu_bridge_host_declined_end` and `tengu_bridge_signed_out_neutral` are present in the build, but what reads them is not visible from the flag definitions.\n\n**Evidence**\n\n`tengu_dazzling_garden`\n\n- Flag `tengu_dazzling_garden`: Not enough to say (read for one account on one subscription tier against v2.1.238; this account: no value returned, anonymous baseline: no value returned, compiled default: on)\n- Flag `tengu_bridge_host_declined_end`: Not enough to say (read for one account on one subscription tier against v2.1.238; this account: no value returned, anonymous baseline: no value returned, compiled default: on)\n- Flag `tengu_bridge_signed_out_neutral`: Not enough to say (read for one account on one subscription tier against v2.1.238; this account: no value returned, anonymous baseline: no value returned, compiled default: on)\n- Area: Remote Bridge\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 4\/5"}