Call.in progress.error vapifault deepgram transcri...
# support
m
All of a sudden, getting this error on inbound calls. Call IDs: 019b09cf-c081-7000-8306-f82bba93fced 019b09cc-79d5-7441-b43a-2987b31a62ed One minute it was working fine, the next minute this happened. No changes to my config.
v
First step: Check if Deepgram or Vapi is experiencing a service outage, as sudden transcriber failures often relate to provider issues. - Visit the Vapi Status Page: [https://status.vapi.ai/](https://status.vapi.ai/) - Visit the Deepgram Status Page: [https://status.deepgram.com/](https://status.deepgram.com/) If either page reports an incident, this is likely the cause. Otherwise, further investigation in your Vapi dashboard's Call Logs is recommended. (According to the [Vapi debugging guide](https://docs.vapi.ai/debugging)) Source: - [Vapi Debugging Guide](https://docs.vapi.ai/debugging)
j
Deepgram is healthy, issue occurs only on VAPI https://status.deepgram.com/
m
Following up, this is the second full outage in less than a month ("Call.in progress.error vapifault transport never connected" issues on Nov 20)
c
Hey! To help track down this issue, could you share: \- 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!
m
Hi Praveen, I provided a couple call IDs in my original message