Agent doesn't respond after using query tool
# support
j
I'm experiencing an issue today where the agent goes silent after receiving a response from the "Query Tool". The agent doesn’t continue the conversation unless i say something first https://cdn.discordapp.com/attachments/1402031340328849530/1402031341138219148/2025-08-03.png?ex=68926ef0&is=68911d70&hm=a8b8535735ec520f0c4d231695caa514313bb30de9454c037a23c7817672d187&
p
I can help you with any difficulty, let's have a chat now and proceed to your project
c
Reset the tool’s custom messages via API ("messages": \[\]) usually restores normal speech behavior..
o
Resetting the message parameter via API has solved the issue for me. I'll observe over the next days, if it remains the same. Thanks for the help. Anyway, I hope there can be something improved in the background on VAPI's side, because I can't always proactivly check, if the issue comes back and reset the parameter by hand. We just discovered the issue due to customer feedback in production.
a
Thanks a lot Oliver, for pointing me to this here and thanks to Kings Big :). But I have to agree with you, this is not a solution, neither can I include in all the prompts now an API POST each time before calling the tool to reset the messages. This is a crappy, even though maybe workaround, and the root cause needs to be fixed by VAPI asap. Also this issue happens randomly in Assistants and in Workflows. Please Kings Big can you fix that soon if possible? Thanks again Oliver!
Please Kings Big can you fix that soon if possible? I have the same issue in Workflows and Assistants, appearing randomly. It can´t be more than a workaround to now include an API post before any tool execution to reset the messages. There must be a fix to the root cause. Thanks in advance! Linkin my post about this with call ids and detail description ;-). https://discord.com/channels/1211482211119796234/1401528870775291914
c
To help track down this issue, could you share: - The call ID - When exactly this happened (the timestamp) - What response you expected to get - What response you actually got instead This would really help us figure out what went wrong!
a
Hey Kings Big! First of all thanks for your brilliant and always helful reactions and willingness to help 💪 . This is a real issue, ruining the user experience and your help is highly appreciated. I had linked the other thread with Call IDs in my answer above your reply. Linkin it here again: Please see -> https://discord.com/channels/1211482211119796234/1401528870775291914 ISSUE in one sentence: The agent (assistand + workflows) idles either before (seldom) or after (often) calling a function and instead of continuing, it waits for any user input. The user needs to say anything to move things forward. The function runs through, I can see that and is successful, but he won´t continue but wait for input before progressing with the prompt. - Thanks for fixing this 😍 . Expected outcome: If the agent calls a function it should run the function and continue with the prompt, instead of requiring the user to say literally anything.
c
Looking into it
3 Views