When trying to call any function through website chat function , just go blank like that . No webhook actions in Logs. Just silence. https://cdn.discordapp.com/attachments/1366026144469749840/1366026144658489344/image.png?ex=680f727c&is=680e20fc&hm=094285032d7d9f2424775b6de88e0f900b39d6a69a194850229f4a7f9acf75e8&

I see you're experiencing an issue with toolcalls not being sent from the Vapi.ai website chat function. To help troubleshoot this problem, I need to understand more about your setup. Could you provide more details about your tool configuration, including: - What type of tool/function are you trying to call? - Is this a custom tool or a default tool? - Have you verified that your server URL is correctly configured and accessible? - Have you checked if the tool is set to synchronous or asynchronous mode? This information will help me provide more targeted troubleshooting steps for your specific situation. Sources: - [Troubleshooting toolcalls not being sent from Vapi.ai website chat function](https://discord.com/channels/1211482211119796234/1326809606671958080) - [Configuration of toolcalls in Vapi.ai website chat function](https://docs.vapi.ai/tools/custom-tools)

@Vapi Support Bot I use custom function for toolcall . It works without any problems with phonecall or with webcall. Just chat problem.

Check if your tool is set to

synchronous

instead of

async

mode, as this is a common issue with chat function toolcalls. Also ensure your response format is correct:

json
{
  "results": [
    {
      "toolCallId": "<your-tool-call-id>",
      "result": "Success message as a single-line string"
    }
  ]
}

For JSON responses, make sure they're stringified and don't contain line breaks. Sources: - [Troubleshooting steps for toolcalls](https://discord.com/channels/1211482211119796234/1342315282198298729) - [Tool call response format](https://discord.com/channels/1211482211119796234/1325000684231196775)

@User Sorry to bother , but it's kinda important for all the testing -_- . And on top of that Publish button started tweaking again

Ensure the correct assistant ID, verify server authentication, check logs for errors, test with simplified configurations..

Again , it works with webcall , but doesnt with chat function. There are no webhook calls in logs when trying to call function in chat . Tried on 2 different projects where i have 1000% working function

dude, it doesn't even send the tool call. Receiving is another matter

Hey DeFerath, really sorry for your experience. If possible, could you record a loom video describing this error/behavior or inconsistency in the dashboard with the steps to reproduce it? That way, I can share this with my team, and we'll take a look. We'll even try to reproduce the same so we can fix it for you. Also, I'll request you to share your assistant ID.

Can you share a Loom video and your assistant ID. Inside the Loom video, I'll be expecting you to describe the steps to reproduce the issue - i.e., why the Tool' calls are not triggering when chatting with the assistant. This way, we can get to know what's not working and eventually get it fixed for you.

shubham its not that complicated, just try tool calling in chat. Its not working in any assistant. Any assistant or any tool is irrelevant. When I call it works, when I chat it doesn't. The issue is not with assistant or tool, its with chat

Team is working on it.

@Shubham Bajaj that's the reply i got from support. How do i change my tools to schema ? cant find any info about it https://cdn.discordapp.com/attachments/1366026144469749840/1367449039897100380/image.png?ex=68149fa9&is=68134e29&hm=90c2d0f6469631d1231588769d1337809c601afd2b6c4911cc16905e51a5e9c3&

Hey, this has nothing to do with the tool call schema. If it's related to something else, let me know.

@Shubham Bajaj i already send email to your support , provided you my assistantid and loom video , it was more than a week ago. Any news ? Its kinda pathetic tbh. Entire testing suit with chat not working and nothing beign done about it. Prev message was from your support btw , quality work here

Hey DeFerath, the team is working on this, and it requires a bit of re-work. You can expect it to be working again by the end of this month.