The result of the tool call is not being received ...
# support
k
I am sending back a response for a tool call request received to my server. Verified that the request is received, processed and a response is returned successfully. The format of the JSON response is correct, JSON keys and string values are enclosed in double quotes. The toolCallId matches the one received in the HTTP request. It's exactly the same issue I've seen in another thread like https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1286635102985523244. I’m providing my latest call ID in case you can resolve it as well, please: 3d16a2a8-cd92-4e70-ab8f-4798e8e013a9 Thanks in advance for your help! I really appreciate it. https://cdn.discordapp.com/attachments/1337284665580453969/1337358583238623293/image.png?ex=67a727bd&is=67a5d63d&hm=1690c740ad4a90d29d1110ea786503b9c2829a31452a5d6fd6a131582ca693aa&
s
@kkhuet. I have looked into the shared call log, response is correct. Can you let me know the issue your experiencing,?
k
Hello. The problem is that the corresponding message (tool-calls-result) does not reach the Client SDK (Chrome), but all other messages do arrive, such as tool-calls. Because of this, I cannot see the results of the tool call. I have this code that logs all other messages except tool-calls-result: // Function that logs any message received from VAPI to the console vapiInstance.on('message', (message) => { console.log('VAPI Message:', message); }); I have set the Async=false option for the corresponding tool. I believe everything is correctly set up: the tool executes, the result reaches VAPI, but then it does not reach the Client SDK. Can you help me? Do you need more info? https://cdn.discordapp.com/attachments/1337284665580453969/1337650090390716436/image.png?ex=67a83739&is=67a6e5b9&hm=3b083cd43d28abb748ab2a132e8d761e75994dc6e1a9f71c240e5af299dffcee& https://cdn.discordapp.com/attachments/1337284665580453969/1337650090608689162/image.png?ex=67a83739&is=67a6e5b9&hm=008647394bdc8e35b8e6a1033ea07a561082f7c36d93d27eec93261b6595e1bc&
s
@kkhuet. can you share your code in a github repo?