Assistant dies after tool call.
# support
j
I have never had this issue before. With a few different tools, upon calling them, our assistant quite literally dies. After a tool call, it goes silent, doesn't respond to live call control, doesn't receive messages from the transcriber, just dies. We tried deleting and recreating one of the tools with the same result. The strange thing is it is working fine with other very similar tools. It's not the webhook response either because we plugged in the same response from a different (working) tool with the same result. We try to talk to the assistant after the tool is called for every single one of these calls, but the transcriber doesn't even pick up anything. We also have messages sent to the assistant with live call control, and even that doesn't revive it. Call IDs c8103337-a97f-4e16-80d7-a9ac2d9eec9e f3fa81a4-5e25-4a31-b519-6324ff9ddeed f2ba4a48-f7e9-4197-8aca-d1069c11fea9 e3f0500b-bb11-4249-9556-0ba7fff64a8c 8edc2751-d708-44a3-b976-2d4912930742 c8103337-a97f-4e16-80d7-a9ac2d9eec9e
@User
Nothing in the webhook logs indicates any issues. All of our tool calls are going through with 200 codes
I guess you can use an "_" for tool call start messages lol
s
@J. looking into it.
logs
🟔 06:25:04:917 Warn: 5s Hang šŸ”µ 06:25:00:911 ElevenLabs (WebSocket #0) Emit Disabled But Requested Event: output. šŸ”µ 06:25:00:865 Queuing Say Request. (Length: 1) (content: "_") šŸ”µ 06:25:00:866 Voice Input Formatted: "", Original: "_" @J. replace the content
_
from request-start, and then it will work.
3 Views