{"version":"2.1.232","anchor":"remote-control-reconnect-budget-is-now-hourly-plus-daily","canonical_anchor":"remote-control-reconnect-budget-is-now-hourly-plus-daily","heading":"Remote Control reconnect budget is now hourly plus daily","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/remote-control-reconnect-budget-is-now-hourly-plus-daily","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Remote Control reconnect budget is now hourly plus daily\n\nRemote Control now allows 3 reconnects per hour and 72 per day, with healthy periods forgiven.\n\n**What**\n\nThe single \"rebuilds in the last hour\" counter is replaced by a budget of 3 recoveries per hour and 72 per 24 hours, and ten minutes of healthy heartbeats forgives the current window so a long-running session is not spent by an old rough patch.\n\n**Details**\n\n- Exhaustion is reported as `heartbeat_budget_exhausted` with a `window_h` field saying which window ran out.\n- The message reads \"the connection to the Remote Control server kept dropping after each reconnect\", with a separate 24-hour variant.\n- The `recovery_exhausted` event now also records the WebSocket `close_code`.\n\n**Evidence**\n\n`the connection to the Remote Control server kept dropping after each reconnect`\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}