Calls suddenly failing with "Unknown Reason" and n...
# support
j
Hi, this morning around 9am EST my calls started failing right when the transferCall step is reached. These calls were succeeding with the same assistant and workflow yesterday. In the "Call Logs" section of the call records, the logs show a model request start (this is the request I would expect to initiate the function call), and that is the last thing. No messages or transcript is populated--the call just abruptly started ending. Any guidance on how to resolve the issue would be greatly appreciated 🙏 How to replicate: 1. Call the assistant (cb7debf9-ba82-4de4-a8c3-0043ee4a78a1), complete the dialogue workflow 2. At the end of the call, the assistant should initiate the transferCall function 3. The call dies instead of transfers (this was successfully transferring until this morning) 4. The Vapi call logs end right before the expected function call with no indication as to why and the "ended-reason" set to "Unknown Reason" Some sample call IDs: - 8b67462d-e863-43fa-b633-f2828941883d - bbf83cca-9df0-431d-9082-285de054b6e2 - df9fbc91-ea5b-45bf-b22a-acaffdd1b275 - 31cf5b16-3f51-46bd-92be-f79340285315
v
@Jeff I'm sorry to hear that you're experiencing issues with your calls. Let's try to troubleshoot the problem together. Based on the information you've provided, it seems like there might be an issue with the
transferCall
function within your assistant's workflow. Since the calls were working previously and have only started failing today, it could be due to a recent change or an external factor affecting the function's execution. To assist you further, I would need to check the details of the assistant's configuration and any recent changes that might have been made. However, since I don't have direct access to the system or the ability to make changes, I recommend the following steps: 1. Review any recent changes to the assistant's workflow or related systems that might have occurred between the last successful call and the first failed call. 2. Check if there have been any updates or outages reported by the service provider that could affect the
transferCall
function. 3. Verify that the
transferCall
function is correctly configured and that all required parameters are being passed correctly. 4. If possible, test the
transferCall
function in an isolated environment to see if the issue persists outside of the normal workflow. If after these steps the issue remains unresolved, it would be best to contact support with the details of your findings, including the sample call IDs you've provided, so they can investigate further. Would you like me to guide you through any specific troubleshooting steps, or is there anything else I can assist you with?
You can continue this conversation by mentioning me in the message.
s
We are looking into it. @Jeff
a
Same issue here. Working fine yesterday and early this morning all assistants with transferCall function are failing
s
Just give us few minutes, we will fix it.
j
Thank you @Sahil--let me know if I can provide any additional information to help!
a
Hello. Do you have an update?
m
@Vapi any update? im losing a ton of money lol
v
@me I understand the urgency of the situation and the impact it is having on your business. Our team is actively working on resolving the issue with the
transferCall
function as quickly as possible. I appreciate your patience during this time. As soon as there is an update or a resolution, I will inform you immediately. In the meantime, if there is any additional information or specific details about your use case that you think might help with the investigation, please feel free to share it. Thank you for your understanding, and rest assured that we are treating this with the highest priority.
s
Fixed.
m
@Sahil it says cartesia is having an outage
s
Can you use different voice provider?
m
@Sahil im using openAI
s
give me latest call_id
m
@Sahil eb2c6772-4483-4fff-b7f1-4c5f06a5827e
s
We pushed fixes like couple of minutes ago
can you retry it once?
@me
m
@Sahil okay will do
m
tried on my end also broken still
s
@mmrdvn provide me your latest call_id
m
@Sahil thank you! c20a135e-c358-4825-b33d-07f6c697a193
s
just checked the logs, assistant successfully forwarded the call.
Did you buy the twilio number from our end?
m
No twilio number is imported
interesting if I use your built in call forwarding in the portal it works. I use the tool call it sucessfully goes through and then doesnt complete the transfer
I can give you the tool ID if that helps
3daac646-ac57-4481-a2bf-e6dc11b1fb92
@Sahil
s
You will need to make the same toolId through API not through the ui
it will work then
for now use forwardNumber field
m
@Sahil we created the tool with the API not with your UI using your json here (modified with our numbers in a test) https://docs.vapi.ai/call-forwarding
s
Sent you a calendly link.
and marking as complete we will discuss this over there
m
Thank you sir