VAPI Workflow Error Help from Gather Node
# support
s
Hey there VAPI Support team! So I am building my existing VAPI assistant within the new workflows feature thats currently in beta you and the team have developed. This is such an awesome addition by the way! Going to fix a lot of problems with inconsistencies with our current VAPI Prompt setup moving over to this solution. However, When going to build this, specifically at the first "gather" step in my workflow... I am receiving the following error underlined in red in my screenshot. Essentially what I am building this gather step for is to gather the "caller_intent" which is to schedule, reschedule, cancel, or confirm an appointment. I have the gather step set up with the following; - Name = caller_intent - Description = The caller's intent for the call. Whether they would like to do any of the following on the call; - Schedule an appointment - Cancel an appointment - Reschedule an appointment - Confirm an appointment - Type = String - Output required = True Then following the gather step I have the following conditions for a branch logic to follow a certain path depending on the gather step; - One branch's logic is when caller_intent contains "schedule" - Second is when caller_intent contains "cancel" - Third is when caller_intent contains "reschedule" - Fourth is when caller intent contains "confirm" - And finally, the fifth is a loop say node (to handle failure), that branches back to the gather step that has the following message "Sorry I did not quite get that, would you like to reschedule, cancel, reschedule, or confirm an appointment?" I am not sure why this gather node has that following error "Node has multiple outgoing edges (excluding failed edges)" Can you assist me in resolving this error? Is multiple logic branches from a condition node following a gather node not possible in the current set up? https://cdn.discordapp.com/attachments/1349476125717299242/1349476126170546176/image.png?ex=67d33d14&is=67d1eb94&hm=059fd10f75e54139b019f0d4eeced43781e4fec1dba6b44e3070b2b0bd0696be&
p
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!
s
I havent tested it yet. Simply because I have this error, I am unable to save any changes I have made, to ensure I can test/publish!
So there are no call id's. Assistant ID is 06319545-281e-438a-8719-2151a9ca3247
@User Please let me know if you need anything else on this. Again, there are no call id’s because i am unable to test it/save it from this error shown in my screenshot above. Not sure how to fix this error in my workflow, considering the context I gave above.
a
Hi, Thanks for trying out our workflows feature! In your gather step, if you mark the field as required, the assistant should enforce that they gather the right variables.
Failed edges is a feature in development, would appreciate any feedback as we build this out 🙂
We currently dont allow loops like this, but we could see it being useful for use cases like this
I think for your use case, it would be helpful for gather to enforce an enum. In the mean time, this should work if you have a few booleans
is_schedule
is_cancel
, etc. but I recognize that this is not ideal