{"version":"2.1.228","anchor":"device-tools-reject-calls-tagged-with-someone-else-s-cloud-s","canonical_anchor":"device-tools-reject-calls-tagged-with-someone-else-s-cloud-s","heading":"Device tools reject calls tagged with someone else's cloud session","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/device-tools-reject-calls-tagged-with-someone-else-s-cloud-s","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Device tools reject calls tagged with someone else's cloud session\n\nTools on your machine refuse calls from a cloud session other than the one being served.\n\n**What**\n\nWhen a cloud session calls a tool on your machine with a `session_id` that does not match the session the device is actually serving, the call is refused with a result explaining the machine is busy with another session and telling the model not to retry in a loop.\n\n**Details**\n\n- Refusals are reported as `tengu_device_tool_refused` with reason `session_mismatch`.\n- Device tools now carry an `analyticsName` used in that reporting.\n\n**Evidence**\n\n`tengu_device_tool_refused`\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}