Increase in pipeline issues in last 24 hours
# support
m
In the last ~24 hours we've started getting a bunch of
call.in-progress.error-providerfault-transport-never-connected
errors. Is this error an updated name for the
call.in-progress.error-vapifault-transport-never-connected
error that has caused issues in the past? (https://status.vapi.ai/incident/528459) I cant find
providerfault
in the
endedReasons
https://docs.vapi.ai/api-reference/calls/get We haven't made any changes recently. example call: e03b7d93-339b-4330-91e7-70d3728c0fec
v
Based on the information I found, the
call.in-progress.error-providerfault-transport-never-connected
error indicates that calls waited 300 seconds but the telephony provider never connected. To investigate this issue: 1. Check your telephony logs for connection problems 2. Contact Vapi support with your call ID (e03b7d93-339b-4330-91e7-70d3728c0fec) 3. Email support@vapi.ai to request a detailed analysis of the issue This error is likely related to network connectivity issues or problems with your telephony provider configuration. Sources: - [Discord conversation about transport never connected errors](https://discord.com/channels/1211482211119796234/1336995626604564551) - [Discord conversation about investigating call issues](https://discord.com/channels/1211482211119796234/1333877747453395014) - [Discord conversation about contacting support](https://discord.com/channels/1211482211119796234/1333747605628391434)
k
Hey Muppet, can you try another call now? It should work for you.
m
Heya we didn’t seem to have as many over night, but just had another one 10 mins ago 44e67952-7e58-4a67-b243-691269017cc2
Just to confirm, is providerfault the new namespace for vapifault errors or are they something that we need to check on our side
We’re still getting a few of these daily @Shubham Bajaj
k
Hey Muppet, the new namespace
vapifault
means error is on our side. could you share all of the call ids with c`all.in-progress.error-providerfault-transport-never-connected` ideally you shouldn't be getting this regularly, can you share all of call Ids. Your issue is priority item for me,
m
Thanks @Shubham Bajaj This list should cover most of the calls that have this error since I submitted the ticket. 8af5528a-23f0-4826-921a-25f6d879e6e1 24c1bf96-caa6-45b5-b3d7-bdacf74130a8 c6e0ddc6-58fe-48a1-823a-0799925f1d53 839feaa3-a117-42c7-a32b-46a634c7d820 310e827f-b710-4571-85cd-982ea618ffd0 6ebd820b-6da0-4d55-a354-22ae1b723735 ad3787f0-d940-4a57-ac29-1c2ad6db212b 44e67952-7e58-4a67-b243-691269017cc2 1d6e46ac-56f9-48de-98a7-7bd3d9585011
1f7a44ac-d779-4ea9-8c56-e2bef3ed0c00
7cc74dd0-7909-4baf-8db6-85dfa548197f
89416fbe-c4f9-422b-a935-8d9d69751e5e
a66a48e9-3061-4b57-9937-48980086e46d
2dcccfe6-f47f-4b02-8b04-ef18764c9ca4
Hey @Shubham Bajaj has the team got any update here?
2aecb3c3-c8db-46ef-938c-7dd077cc0494
k
Allow me sometime to get back to you.
🟢 15:07:05:998 Call 89416fbe-c4f9-422b-a935-8d9d69751e5e Done. ([call.in](http://call.in)-progress.error-providerfault-transport-never-connected) 🟢 20:35:39:627 Call a66a48e9-3061-4b57-9937-48980086e46d Done. ([call.in](http://call.in)-progress.error-providerfault-transport-never-connected)
Hey I just confirmed the issue on twilio side, can you check the twilio logs for the following calls and share with me in DM as well. Apologies for the delay and confirmation. https://cdn.discordapp.com/attachments/1364788489236779049/1366784337655234610/image.png?ex=6812349b&is=6810e31b&hm=763e8a6e3a6a974d3cca8826076353cad4c3e3008244a2fc674217eb24cb4145&
3 Views