{"version":"2.1.286","anchor":"bridge-poll-intervals-swapped","canonical_anchor":"bridge-poll-intervals-swapped","heading":"Bridge heartbeat timing uses its intended interval when at capacity","tier":"notice","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/bridge-poll-intervals-swapped","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Bridge heartbeat timing uses its intended interval when at capacity\n\nWhen a multisession bridge is at capacity, the next heartbeat is now timed by the heartbeat interval and capped by the at-capacity poll interval\n\n**Unclear.** It is unclear whether this corrects a mistake or deliberately changes the timing.\n\n**What**\n\nWhen Claude Code's bridge is handling several sessions and is at capacity, it waits between heartbeats, which are regular check-ins that show it is still running. The two timing values used in that wait have swapped roles:\n\n- The next heartbeat is now scheduled using `non_exclusive_heartbeat_interval_ms`.\n\n- The wait is capped by `multisession_poll_interval_ms_at_capacity`.\n\nBefore, the next heartbeat was scheduled from the at-capacity poll interval.\n\n**Why**\n\nThis changes how often bridge sessions check in while at capacity.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}