Tools on your machine refuse calls from a cloud session other than the one being served.
What's wrong with this entry?
When 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.
- Refusals are reported as
tengu_device_tool_refusedwith reasonsession_mismatch. - Device tools now carry an
analyticsNameused in that reporting.
tengu_device_tool_refused
Strings lifted out of the shipped bundle, so the claim above can be checked against them.