{"version":"2.1.225","anchor":"bridge-heartbeats-now-count-as-proof-of-auth","canonical_anchor":"bridge-heartbeats-now-count-as-proof-of-auth","heading":"Bridge heartbeats now count as proof of auth","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225\/e\/bridge-heartbeats-now-count-as-proof-of-auth","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225","markdown":"### Bridge heartbeats now count as proof of auth\n\nA successful Remote Control heartbeat now clears stored auth failures, so you get fewer spurious re-login prompts.\n\n**What**\n\nA successful bridge heartbeat clears accumulated authentication-failure state instead of leaving the counter to age out on its own.\n\n**Details**\n\n- the CCR client gained an `onRequestAuthOk` option, invoked next to `resetHeartbeatStreak()` on each successful heartbeat\n- the bridge supplies a callback that resets its auth-failure counter and calls the existing `onAuthProven` hook\n\n**Evidence**\n\n`onRequestAuthOk`\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 0\/5"}