{"version":"2.1.248","anchor":"pending-remote-control-requests-are-now-closed-out-as-detach","canonical_anchor":"pending-remote-control-requests-are-now-closed-out-as-detach","heading":"Pending Remote Control requests are now closed out as detached","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/pending-remote-control-requests-are-now-closed-out-as-detach","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Pending Remote Control requests are now closed out as detached\n\nRemote Control shutdown now closes out pending requests as detached instead of abandoning them.\n\n**What**\n\nWhen Remote Control shuts down, whether the host exits, the feature is turned off, or the transport tears down, every request or dialog still waiting on a remote answer is now completed with a `detached` outcome instead of being abandoned. Reachable by anyone using Remote Control, with no flag.\n\n**Details**\n\n- The cleanup walks the outstanding request map, deletes each entry, calls its handler with `{ behavior: \"detached\" }` and returns how many it closed.\n- `detached` is a new terminal outcome; it does not appear in v2.1.247 at all.\n\n**Evidence**\n\n`behavior: \"detached\"`\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}