Call.in progress.error vapifault deepgram transcriber failed Vapi AI #support

Call.in progress.error vapifault deepgram transcri...

dunecat

11/19/2025, 12:13 AM

Hi, still getting this error above after the Deepgram issue today has been "resolved" ... My transcriber config is: "transcriber": { "model": "nova-3", "keyterm": [ "Term 1", "Term 2", "Term 3" ], "language": "en-AU", "numerals": true, "provider": "deepgram" } Some call IDs that were affected: 019a9956-d917-7444-a16e-3bce9b02d665 019a9804-4c8f-7441-a899-3ccf2ec6f238 019a97e4-c4c8-7773-9396-176672cbeada 019a97dd-8ed7-7110-a945-daf5f2a1a7d6 I've had to switch transcribers entirely for now but want to use Deepgram again - please help!

Vapi Support Bot

11/19/2025, 12:14 AM

Suggestion: To work around persistent Deepgram transcriber failures, try integrating Deepgram as a custom transcriber in Vapi. Set up a Node.js server using the following snippet:

Copy code

bash
npm install ws express dotenv @deepgram/sdk

Create a

.env

file with your Deepgram API key, then follow the [custom transcriber guide](https://docs.vapi.ai/customization/custom-transcriber) to stream audio from Vapi to Deepgram and return transcripts. This lets you control error handling and may restore Deepgram support while the built-in provider is unstable. Source: - [Custom transcriber integration with Deepgram](https://docs.vapi.ai/customization/custom-transcriber)

Chiranjeet Mishra

11/20/2025, 10:56 PM

Could you please run a few test calls now to see if you are still encountering the same error? We were unable to reproduce the issue on our end, so confirming whether it persists on your side will help guide next steps. Once you have a recent call ID, feel free to share it here and we’ll take another look right away.

dunecat

11/21/2025, 11:00 AM

It cleared up for two days and now it's back. New call IDs are: 019aa5e0-c5bb-7000-959c-3fa048a53501 019aa5e1-638c-7114-ac3b-5a9324cdfaa7 019aa60e-9f57-7cc0-bf7e-ef7947413884 Thanks

dunecat

11/21/2025, 11:01 AM

This is a production service so if you could give me a quick response that would be great!

dunecat

11/21/2025, 11:36 AM

Copy code

{
  "id": "log-7",
  "level": 50,
  "time": 1763724751990,
  "timestamp": 1763724751990000000,
  "severityText": "ERROR",
  "severityNumber": 17,
  "body": "Deepgram WebSocket error",
  "attributes": {
    "category": "transcriber",
    "callId": "019aa62f-d8e0-7aa7-b33a-db1bffff5621",
    "orgId": "9a92caa1-16d9-413f-87b0-8f8024203ca0",
    "provider": "deepgram",
    "error": {
      "message": "Deepgram connection failed with status 400 (Request ID: fb3a0866-804d-4c0f-9361-6d8781d22f68)"
    }
  }
}

dunecat

11/22/2025, 5:32 AM

I've resolved this - too many keywords

Chiranjeet Mishra

11/25/2025, 10:45 AM

Glad you were able to get this resolved. If anything else comes up or you need further assistance, we’re here to help.

Previous Next