{"version":"2.1.248","anchor":"the-background-bridge-resumes-sessions-cut-off-by-a-restart","canonical_anchor":"the-background-bridge-resumes-sessions-cut-off-by-a-restart","heading":"The background bridge resumes sessions cut off by a restart","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/the-background-bridge-resumes-sessions-cut-off-by-a-restart","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### The background bridge resumes sessions cut off by a restart\n\nThe remote-control bridge now re-registers sessions it was running when it restarted.\n\n**What**\n\nWhen the headless remote-control bridge shuts down it now records which sessions were active, and on restart it re-registers and re-queues them instead of losing them.\n\n**Details**\n\n- The saved list and its timestamp are read back from the bridge's pointer file, and only reused if the timestamp is inside a fixed freshness window.\n- Startup logs `re-queuing N session(s) interrupted by the previous shutdown`, and each resume reports success or `env_reuse_declined`.\n- Persisting the list on shutdown is controlled by `tengu_daemon_upgrade_defer_busy`, which falls back to on, so absent remote config the daemon does persist.\n- Pointer-file writes moved from a bare hourly timer onto a write queue.\n\n**Evidence**\n\n`bridge_shutdown_requeue`\n\n- Flag `tengu_daemon_upgrade_defer_busy`: Not enough to say (read for one account on one subscription tier against v2.1.248; this account: no value returned, anonymous baseline: no value returned, compiled default: on)\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}