{"version":"2.1.281","anchor":"bridge-stops-work-items-that-carry-an-unsupported-mode","canonical_anchor":"bridge-stops-work-items-that-carry-an-unsupported-mode","heading":"Bridge stops work items that carry an unsupported mode","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/bridge-stops-work-items-that-carry-an-unsupported-mode","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Bridge stops work items that carry an unsupported mode\n\nRemote Control now stops incoming work that carries an unsupported mode instead of trying to run it\n\n**Unclear.** The finding does not say which modes exist or where they come from.\n\n**What**\n\nThe bridge is the part of Remote Control that picks up incoming work for this machine. If a piece of work arrives with a `data.mode` value set, the bridge now stops it once. It logs \"Stopping work item with an unsupported mode\" and records the event `tengu_bridge_work_mode_unsupported`.\n\nThe bridge also regularly sends a heartbeat, a small \"still here\" signal. While it waits because it is full, it now tracks when the next heartbeat is due instead of sending one for every skipped item. On shutdown, cleaning up worktrees (separate working copies of a project) now has a time limit for reading.\n\n**Why**\n\nWork this version cannot handle is ended cleanly rather than half-handled. A full bridge sends fewer heartbeats, and shutdown should not wait forever on worktree cleanup."}