{"version":"2.1.225","anchor":"remote-control-new-terminal-error-reasons-and-clearer-failur","canonical_anchor":"remote-control-new-terminal-error-reasons-and-clearer-failur","heading":"Remote Control: new terminal error reasons and clearer failure surfacing","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225\/e\/remote-control-new-terminal-error-reasons-and-clearer-failur","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225","markdown":"### Remote Control: new terminal error reasons and clearer failure surfacing\n\nRemote Control failures now tell you what actually broke and that you can rerun \/remote-control to retry.\n\n**What**\n\nBridge failures are now distinguished by reason and kind instead of collapsing into one generic error, and the message tells you how to retry.\n\n**Details**\n\n- New failure reasons `request_rejected`, whose message is assembled as \"Remote Control server rejected the request (HTTP ...) \u2014 run \/remote-control to retry\", and `malformed_response`.\n- HTTP classification separates \"oauth_rejected\" (non-terminal) from \"transient\" and \"rejected\" (terminal).\n- Failures are reported with an explicit kind, \"terminal\" or \"auth\", including the org-policy case.\n- App state carries `replBridgeError` and `replBridgeErrorKind`.\n\n**Evidence**\n\n`run \/remote-control to retry`\n\n- Area: Remote Control\n- Names: `\/remote-control`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}