{"version":"2.1.248","anchor":"a-reconnect-backoff-schedule","canonical_anchor":"a-reconnect-backoff-schedule","heading":"A reconnect backoff schedule","tier":"internal","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/a-reconnect-backoff-schedule","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### A reconnect backoff schedule\n\nA reconnect backoff and heartbeat schedule appears, with no identifiable consumer.\n\n**What**\n\nA new set of connection-retry constants appears: retries start at 1s and double up to a 30s cap, a connection must stay up 60s to count as healthy, 10 consecutive failures stop retrying, and a presence heartbeat goes out every 15s. Which connection uses these is not identifiable from the build.\n\n**Evidence**\n\n`maxConsecutiveFailures`\n\n- Area: Internals\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}