{"version":"2.1.227","anchor":"remote-session-connection-learns-liveness-probes-and-reconne","canonical_anchor":"remote-session-connection-learns-liveness-probes-and-reconne","heading":"Remote-session connection learns liveness probes and reconnect resync","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/remote-session-connection-learns-liveness-probes-and-reconne","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Remote-session connection learns liveness probes and reconnect resync\n\nRemote sessions can answer liveness probes and resync after a dropped connection.\n\n**What**\n\nThe long-lived connection to remote sessions can now tell the server it accepts liveness probes, report the heartbeat interval it is using, and respond to a probe frame. After a dropped connection it runs a resync, and it will not accept a server-suggested heartbeat interval that outlives the current auth token.\n\n**Details**\n\n- Turned on by an `advertiseLivenessProbeSupport` option on the transport; nothing in this build was found to set it.\n- Probes are logged as `cli_sse_liveness_probe_received`; unrecognised transient frame types log `cli_sse_unexpected_ephemeral_type`.\n- A heartbeat is forced immediately after reconnect, spaced for probes.\n\n**Evidence**\n\n`cli_sse_liveness_probe_received`\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}