{"version":"2.1.247","anchor":"endless-stream-reconnection-is-built-but-off-in-this-build","canonical_anchor":"endless-stream-reconnection-is-built-but-off-in-this-build","heading":"Endless stream reconnection is built but off in this build","tier":"soon","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/endless-stream-reconnection-is-built-but-off-in-this-build","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Endless stream reconnection is built but off in this build\n\nThe cloud event stream could redial forever, but nothing turns that on so it still gives up.\n\n**What**\n\nThe cloud session's event-stream client can be told to keep redialling forever instead of giving up after 5 reconnect attempts. Nothing in this build turns it on, so behaviour is unchanged: the budget runs out and the stream closes.\n\n**Details**\n\n- When on, exhausting the budget keeps retrying at the maximum backoff delay indefinitely, logs the attempt count as `\u221e`, stops firing the reconnecting callback, and sends a one-shot telemetry event the first time it passes the budget.\n- The mode reads from two places: a `keepStreamRedialling` config key, which nothing in the build ever writes, and an instance flag set only by a method that has no caller anywhere in the bundle.\n- The intent is a machine that is serving device hooks or remote tool calls for a cloud session and must stay dialled in.\n\n**Evidence**\n\n`remote_connect_redialling_past_budget`\n\n- Area: Cloud Sessions\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}