ambitious-aqua•3mo ago
Workflows - new integrated TOOL - bug / issue
Hi Vapi, thanks for the new feature to call tools directly in the WORKFLOW node. I noticed an issue: The tool call gets triggered, but then stays idle, if no "Messages to be spoken during different stages of tool execution are configured". And if you have messages configured, it waits for a user input after each single message spoken (like "I open the calendar." - idle - user says something ... - next message triggers "hold on I am checking timeslots now" - idle ---- user says "hello still there?" --- "yes, here are the timeslots..." etc. Call ID: da334a00-abbd-4e87-991e-058af24ee3d0, 2be3fec1-ded2-49a6-805b-e75f6f7ed068. It should neither be idle when no message is configured, nor if a message is configured. It should just execute and finish the tool call with the result returned, including speaking the "Request Start", Request Complete" Messages, without waiting for a user input at each step. Just like if I use a tool call as a separate node.
8 Replies
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
Vapi
Customer Support Team
ambitious-aquaOP•3mo ago
Also I must add, I found out that when I used e.g. a Query_tool inside a workflow node that came before the actual node, the "repetition issue" with the AI repeating the same questions again for multiple times was more prevalent. Not sure how this is related, but it happens consistently.
ambitious-aquaOP•2mo ago
@Vapi Any update on this ? The tool calls gets triggered, completes but then the node stays idle after completion. See above. Here is also a new example: Call ID: 3500485a-dc3b-4159-931e-35fcee97a76a, as you can see in the screenies, the tool call worked, but Node stays idle, until the user to says something (literally anything, just some utterance), it won´t continue to process the prompt instructions in the node. It just stays idle til the user utters something. The only workaround now is to setup a tool status message, when the tool call completed successfully like asking "is that ok, user?" so u need to trigger user to say something (irrelevant what he says) to move forward. -> This is not a good solution, as you force the user to say something, just to move forward.
Hey, the workflows is currently still under development and the tech team is working on it. Hang in there.
ambitious-aquaOP•2mo ago
Sure, will hang in there.... Workflows is a "released" feature, as well as "toolcalls within nodes". I am just giving my 5cts bug reporting feedback, so you guys know. Also we already try to build production agents on workflows and spend like 100s of hours into it, but it is still buggy. So I can´t wait to see you fixing it and further developing it. I fully understand you guys are still working on it, but you need to fix this, as it concerns released features and we really do not want to need to rethink our decision for VAPI workflows, until workflows are fixed.
@Vapi , @Aditya Papriwal, by the way it starts happening in normal assistants (not limited to workflows), too: Call ID: 1fdd9a3d-630d-4ccd-a7f8-84ad87363105 . See end of call when completing book appointment function, it idles until the user says anything instead of smoothly continuing w/o user input after tool call completion.
Let me add, that this seems related to the other support post here in DC "Agent doesn't say anything after recieving information of the query tool" - the same problem might be the root cause.
Thanks for sending the call id. We will look at the logs and get back to you
ambitious-aquaOP•2mo ago
Thanks Kyle, awesome! Just fyi - I guess this is related to this one...also happens in Assistants as I found out later.. https://discord.com/channels/1211482211119796234/1401528870775291914 and https://discord.com/channels/1211482211119796234/1402031340328849530
Currently for the query tool, the workaround for the assistants is to use an empty
request-start message and then the assistant will iterate the tool call result with no issue. We are continuing to look into this issue