{"version":"2.1.247","anchor":"clearer-explanations-when-a-call-to-an-attached-machine-fail","canonical_anchor":"clearer-explanations-when-a-call-to-an-attached-machine-fail","heading":"Clearer explanations when a call to an attached machine fails","tier":"notice","area":"Remote Tools","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/clearer-explanations-when-a-call-to-an-attached-machine-fail","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Clearer explanations when a call to an attached machine fails\n\nFailed calls to an attached machine now explain what went wrong, including calls dropped from the queue.\n\n**What**\n\nFailures calling a tool on another machine now say which of several things happened, including a call withdrawn while still waiting in the queue, which reports that most likely nothing ran on the other side.\n\n**Details**\n\n- New telemetry outcomes `host_withdrawn`, `stalled` and `host_gone`, plus a trace when a refusal could not be verified.\n- Hosts reached over the session channel report that the machine did not answer a liveness check, instead of the generic not-reachable message.\n- Permission handling and the tool-listing fallback now treat session-channel hosts the same as bridge hosts.\n\n**Evidence**\n\n`so it was withdrawn while still queued here`\n\n- Area: Remote Tools\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}