{"version":"2.1.247","anchor":"tool-results-that-never-reached-the-cloud-session-get-their-","canonical_anchor":"tool-results-that-never-reached-the-cloud-session-get-their-","heading":"Tool results that never reached the cloud session get their own message","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/tool-results-that-never-reached-the-cloud-session-get-their-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Tool results that never reached the cloud session get their own message\n\nWork done locally for a cloud session that never arrived now gets its own explanatory message.\n\n**What**\n\nWhen work this machine did for a cloud session fails to arrive, you now see text saying the result of that work, a command it ran or files it synced, did not reach the session before it stopped waiting.\n\n**Details**\n\n- Previously only hook responses had an undelivered explanation; tool responses now have their own.\n- Cancelling a request now gives up on in-flight tool responses as overtaken, matching how hooks were already handled.\n\n**Evidence**\n\n`The result of work this machine did for the cloud session (a command it ran, or files it synced) did not reach the session before it stopped waiting for it.`\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}