Tools not being triggered during call
# support
d
During my conversations with my voice bots, none of the tools are being triggered. They were working just fine yesterday so this tells me there is a bug
c
Hi there, Thank you for your message. Our team is currently out of the office. We operate Monday through Friday, from 9:00 AM to 8:00 PM Pacific Standard Time (PST). We’ll get back to you as soon as possible during our normal business hours. If your message is urgent, please mark it accordingly or include “URGENT” in the subject line, and we’ll do our best to respond promptly. Warm regards, Vapi Customer Support Team
v
Quick Action: To diagnose why your tools aren't triggering, go to your Vapi dashboard and check the call logs:
Copy code
text
1. Navigate to: Observe > Call Logs
2. Review the "Tool Execution" section for errors or skipped steps.
This will show you if tools are being called and any errors that occurred, helping you pinpoint the issue quickly. If you see errors, try testing each tool individually in the dashboard's Tools section to isolate the problem. (Reference: Vapi Debugging Guide) Source: - [Debugging voice agents documentation](https://docs.vapi.ai/debugging)
m
@Devin I might be able to help, do you want to get on a call and share with me whats going on?
c
Hi Devin, If you're encountering issues with tool calls not working properly, it might be related to server validation failures or issues with tool message handling. Please ensure that the tool call setup aligns with the specifications outlined in our [API documentation](https://docs.vapi.ai/api-reference/webhooks/server-message). Here are a few checks you can perform: - Confirm that the tool call messages are correctly formatted according to the schema. - Ensure that the arguments for function calls are properly defined and matched. - Verify that authentication and authorization for tool usage are correctly implemented. If you receive specific error messages, refer to the [error codes documentation](https://docs.vapi.ai/api-reference/webhooks/server-message) to understand the issues and their resolutions.
2 Views