https://vapi.ai/ logo
Join Discord
Powered by
VAPI Workflow issues
# support
j
Hello I have recently created a new conversational agent in workflows although we are experiencing a ton of issues. The main issue is that the assistant randomly starts repeating the same message within the conversational node and ends up breaking itself. Example: Call ID: aff34aec-6d72-4d54-830f-7ddf5cf09b38 Timestamp: 1:25 We are also noticing issues with transcription. Are there any enhanced English transcription settings we could use? We are currently using: Deepgram Nova 2
j
BUMP
c
Hey James, we're on it and will get back to you soon.
j
Hey Sahil, I am now getting this error and cant access my workflow at all?? Workflow ID: d1ad4750-4fd6-4803-b25e-c857c6210da4 https://cdn.discordapp.com/attachments/1391356372360237167/1392341336274894848/image.png?ex=686f2e6b&is=686ddceb&hm=9ba92a061fbdd5f65ac6af15615860211349cf92290ee60858759cd6c2a1ede4&
c
Sorry for the delayed response, we are still working on your request. Thank you for your patience
j
My team will be discontinuing the usage of VAPI workflows until we know it is safe for production 🙂
Squads seems to be working well as a temp replacement although we need to remove that transferring you now message as we want it to flow as if it was one continuous conversation, is this possible?
c
Yes you can modify the transfer request-start message. If you would like to update it through the API documentation tool, I will provide the link below and the field you need to edit. Use your VAPI API Key as the bearer token and use SquadId as the id. This is the field to modify --> Here is the tool to update the squad transfer message -->
j
Hey Kyle, thanks a ton for this! It has stopped the Squad agents from saying the default message although we have noticed there is a bit of a delay between the next agent picking up from where the last one left off. Also noticed that the agent make a weird noise when it does the transfer call ID: 8701ce2e-b290-4ab0-b6ea-44f655555f62 - 0:13
c
Hey James, Thank you for reaching out. Please note that our team does not operate over the weekend. We'll be back in the office on Monday and will dive straight into your issue then to determine the best way forward.
j
Thanks so much 🙂
c
Hey James, Thanks for reaching out! We're currently swamped with a bunch of tickets and it's taking us longer than usual to get back to everyone. I know waiting isn't fun, but we want to make sure we give your issue the attention it deserves rather than rushing through it. We'll circle back with you soon to get this sorted out.
Copy code
{
  "type": "request-start",
  "blocking": false,
  "content": " \"\"",
  "conditions": [
    {
      "param": "destination",
      "operator": "eq",
      "value": "New Assistant2"
    }
  ]
}
it looks like there is some empty spaces in the request start message, which may have caused the assistant to say "the" before transferring. you can set the request start message to none and it should solve it
j
Hey Kyle, I put nothing in the message string and had this output: { "members": [ { "assistantDestinations": [ { "message": "", "type": "assistant", "assistantName": "New Assistant2" } ] } ], "membersOverrides": {} }
c
Hey James, I wanted to let you know that we're managing a high volume of support requests at the moment, so our response time might be a bit slower than usual. I truly appreciate your understanding and will get back to you as soon as possible!  Thanks again for your patience!
j
Hey guys any updates with how to fix the above SQUAD error?
c
Sorry for the delayed response. Could you please send the squad config so we can review it? Easiest way to get that is by using the tool in our documentation for sending API requests. All you need is the bearer token (your vapi API key) and squad id then send request. I'll provide the link down below:
2 Views
PreviousNext
Powered by