{"version":"2.1.259","anchor":"heartbeat-cadence-beats-can-now-be-skipped-when-other-traffi","canonical_anchor":"heartbeat-cadence-beats-can-now-be-skipped-when-other-traffi","heading":"Heartbeat cadence beats can now be skipped when other traffic already confirmed liveness","tier":"internal","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259\/e\/heartbeat-cadence-beats-can-now-be-skipped-when-other-traffi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259","markdown":"### Heartbeat cadence beats can now be skipped when other traffic already confirmed liveness\n\nA scheduled heartbeat is skipped when a recent events upload already proved the connection is alive.\n\nThe CCR background job client can now skip a scheduled heartbeat tick if a non-ephemeral events POST already succeeded recently, logging `Heartbeat skipped (events beat)`. This reduces redundant heartbeat traffic.\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}