{"version":"2.1.228","anchor":"heartbeats-report-idle-time-and-fire-an-extra-beat-after-a-s","canonical_anchor":"heartbeats-report-idle-time-and-fire-an-extra-beat-after-a-s","heading":"Heartbeats report idle time and fire an extra beat after a stale reconnect","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/heartbeats-report-idle-time-and-fire-an-extra-beat-after-a-s","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Heartbeats report idle time and fire an extra beat after a stale reconnect\n\nSession heartbeats now say how long you have been idle and advertise probe support under a new name.\n\n**What**\n\nHeartbeats now include how many seconds the session has been idle, and the field advertising probe support was renamed to `supports_heartbeat_probe`.\n\n**Details**\n\n- After reconnecting, if the last good heartbeat is older than 1.5 times the current interval and no rate-limit response was seen recently, one extra beat is sent and reported as `cli_heartbeat_reconnect_stale_beat`.\n\n**Evidence**\n\n`cli_heartbeat_reconnect_stale_beat`\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}