I'm having issues with the assistant; when a tool is activated, it goes silent despite being configured with the Async option.

Hi there! I understand how frustrating it can be when your assistant goes silent during tool activation 🔧 I can help explain why this might be happening with your Vapi assistant and provide some troubleshooting steps, even though I don't have visibility into your specific implementation details. ## Why This Happens When the Async option is enabled, several issues can occur: 1. **Automatic Success Messages**: According to [Discord discussions](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1342336047589359618), when a tool is set to async, the client automatically sends back a

tool_call_result

message with result "Success" which can interrupt and confuse the assistant. 2. **Tool Call Result Limitations**: When using async, the tool call result might only show "Success" rather than the full result, as mentioned in [Discord conversations](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1340737584309211136). 3. **Prevention of Start Messages**: The async option can prevent start messages from being spoken, which might contribute to the silence you're experiencing, according to [user reports](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1341585041624666122). ## Troubleshooting Steps Here are some steps you can take to resolve this issue: 1. **Review Your Tool Configuration**: Check if your async setting is appropriate for your use case. According to the [Vapi documentation](https://docs.vapi.ai/tools-calling), setting async to "true" allows the AI to continue without waiting for responses, but this might cause issues. 2. **Check Message Configuration**: If no start message is provided for a tool, the assistant might default to using random filler messages. You can explicitly set an empty messages array for your tool to prevent this.

Hey! To help track down this issue, could you share: - The call ID - What response you expected to get - What response you actually got instead This would really help us figure out what went wrong!

Call ID 14fe2f55-d423-4d65-9e13-8e6a02c08a02 Expected response "Estoy guardando la receta" Actually response Silence until it finish the tool call and response "Oido, receta guardada" If i configure the tool with messages it doesnt even speak when the tool get activate.

Hey Noobhealer, when you set your Async to true for your tool, we don't wait for its response and instead move forward and set it to success. That's why your tool called response is not being used. Secondly, you are not returning the response in the expected format. You have to return the response in the expected format which you can check out by going through this documentation . Once you are done with these two changes, your tool call will work as it is expected. Change Async true from default and return the response in the expected format.

Hello @Shubham Bajaj I think you misunderstood my team mate @Noobhealer . The assistant it's not "moving forward" it's waiting for the answer, and it shouldn't wait as it is set to async I agree the answer format is incorrect, but in this case, it does not matter, as we are not using the answer.

@Jorge @Noobhealer If you don't return the response in expected format then it goes to failed message type which eventually leads to the silence.