{"version":"2.1.242","anchor":"the-remote-control-bridge-recovers-when-the-server-forgets-i","canonical_anchor":"the-remote-control-bridge-recovers-when-the-server-forgets-i","heading":"The remote-control bridge recovers when the server forgets it","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/the-remote-control-bridge-recovers-when-the-server-forgets-i","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### The remote-control bridge recovers when the server forgets it\n\nRemote control re-registers and reattaches your sessions if the server forgets this machine.\n\n**What**\n\nIf the server replies 404 to the bridge's work poll, meaning it no longer knows this machine, the bridge now re-registers itself and resumes instead of shutting down, re-attaching every live session. It is controlled remotely by `tengu_glimmering_glade`, which is on when the server says nothing.\n\n**Details**\n\n- Re-registration asks to reuse the same environment id, up to 3 attempts; if the server hands back a different id, the replacement is deregistered and the bridge gives up.\n- On success it adopts the new environment secret and re-queues each active session.\n- Verbose output shows `Environment re-registered; resuming poll.` or `Re-registration failed; retrying after backoff.`\n- New event `tengu_bridge_env_reregister` with outcomes register_rejected, register_transient, replaced, reregistered, recovered, requeue_dropped, gave_up, plus a `bridge_env_reregistered` log line.\n\n**Evidence**\n\n`tengu_bridge_env_reregister`\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}