{"version":"2.1.271","anchor":"new-fork-conversation-remote-control-op-with-fork-failure","canonical_anchor":"new-fork-conversation-remote-control-op-with-fork-failure","heading":"New 'fork conversation' remote-control op with fork-failure telemetry","tier":"internal","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/new-fork-conversation-remote-control-op-with-fork-failure","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### New 'fork conversation' remote-control op with fork-failure telemetry\n\nFailed 'fork conversation' remote-control attempts now log dedicated telemetry and a clear error\n\n**What**\n\nA new function handles a failed attempt to fork a conversation via remote control, logging `rc_fork_conversation` telemetry and returning a structured result: `{forked: false, error: 'fork failed', reason: 'fork_failed'}`.\n\n**Why**\n\nThis gives failed conversation-fork attempts a clear, trackable error instead of an unhandled or ambiguous failure.\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}