New to Vapi - are all the complex workflows this buggy? I was adjusting the Voice speed on one of my Vapi assistants (from 1.0 down to 0.7) and now whenever I reach that assistant via my Squad, the Assistant the voice comes out SUUUPPPPEEEEERRRRR SSSSSLLLLLOOOWWWWW (like that). Even after adjusting my Voice speed back to default, deleting the squad and starting again, the error is still there!! What the hell? How can I build a business on tech like this?

Hey! 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!

Hey! I've woken up this morning and recreated the Squad again, and the slow speech bug has stopped, but now my 'Call Transfer Assistant' is not forwarding the call to the call Forwarding phone number. Would you kindly take a look at that one for me please? Call ID: 29d00d39-98a4-4594-994e-4cc6b2fb36d6 Timestamp: 13 Mar 2025, 07:44:42:357 (when error occurs) Expected response: Transfer to my Forwarding Phone Number (as described in the 'Functions' section of the Assistant on the Vapi Platform (to +447949916620 - my personal number) Actual response: [ERROR] transfer-destination-request failed validation. No

destination

. [ERROR] transfer-destination-request Server URL Error: Request failed with status code 404 Another way of describing this issue: When I connect my Twilio number directly with my 'Call Transfer Assistant', the call transferring works. But when I connect my Twilio number with the Squad, and then the call is routed to my 'Call Transfer Assistant' via another assistant, my 'Call Transfer Assistant' loses the ability to transfer the call to my 'Forwarding Phone Number' (the only thing she's designed to do). Thank you for your help!

Hey Bilbo, I just took a look through the call logs and the assistant did properly transfer successfully. It looks like in this specific case, the call was transferred successfully to the assistant, and then when it generated it's response it was interrupted so it stopped. This new agent (the call transfer assistant) was instructed to transfer the call and fired the function with empty arguments and that caused the 404 error. My recommendation would be to first upgrade your LLM, 3.5T is a last gen model and is notoriously unreliable at firing functions. Then, make sure your server URL is returning the correct transfer destination and you should see the model fire it appropriately. Give it a shot and let me know how it goes! Here to help you get up and running.