tonight my calls just started failing. when i call one of my vapi (twilio numbers) it says "we are sorry an application error has occurred". Even more concerning - it did not fallback to my fallback number! I thought if a call failed to connect to vapi it would connect to the fallback destination? I also I went into call logs to see if i could figure out anything and all the call logs are gone. Is vapi down? At minimum when vapi doesnt connect the fallback destination needs to work. Someone please tell me this is getting fixed. https://cdn.discordapp.com/attachments/1328956494384726077/1328956494573735946/Screenshot_2025-01-15_at_12.18.27_AM.png?ex=678896af&is=6787452f&hm=522477e7b3447b81d793c053c28ede87a4ed8e0078d574534cdf3cd7b3367626&

@isaiahbuilds I'm sorry to hear about the trouble you're experiencing with your calls and the fallback mechanism. It sounds like there may be an issue with the VAPI service or a configuration problem that's preventing the fallback from functioning as expected. Firstly, the message "we are sorry an application error has occurred" typically indicates that there's an issue with the application logic or the VAPI service itself. The missing call logs could also be a symptom of a service disruption. Regarding the fallback destination not working, this should indeed trigger if the VAPI fails to connect the call. There might be a configuration issue or a service outage that's affecting this feature. To address this, I recommend the following steps: 1. Check the status page of the VAPI provider to see if there are any reported outages or incidents that could be affecting the service. 2. Review your VAPI configuration to ensure that the fallback number is correctly set up. 3. If the issue persists and you're unable to resolve it with the above steps, please reach out to the support team for further assistance. If you need immediate help with checking the service status or reviewing your configuration, please let me know, and I can assist you further. If you believe the issue has been resolved or if you need to close this support ticket, just let me know, and I can close the ticket for you.

yeah this issue is definitely not resolved. and the calls that don't connect need to 100% go to the fallback destination. This part is one part that should never ever fail. very concerning. we're getting ready to release this to our customers in 5 days and now im having second thoughts. also it's not an issue with our configuration - no changes between the time it was working and when it stopped.

I'm getting the same issue

+1 same issue

mine seems to be back working again now

seems to be resolved for me too

@isaiahbuilds @MS @bowen could you all share a recent Loom video so I could take a look, and at the same time please share your organization ID?

@Shubham Bajaj sorry I don't have a screenshot or video of the issue I was experiencing. I had noticed it first when I was trying to connect using a web snippet. I then went to the Vapi dashboard and tried to call the assistant directly but the connection was not getting through. I'll PM you my org ID.