VAPI•4w ago

call.in-progress.error-vapifault-worker-died

Call-ID: 019ac00d-e0a2-7dd8-8f66-bd69662339bc
Account email: amin+vapi@tavan.se

I followed this call while is was running. It was a longer call (25-28min) and when it was ended this was the results.

I do not want to loose the transcripts, voice-recording etc. Is it possible to get this?

Vapi Support BotAPP•11/26/25, 1:02 PM

You can try retrieving the call's transcript and recording using the Vapi API with your Call ID. Here’s a code snippet in JavaScript:

import { VapiClient } from "@vapi-ai/server-sdk";
const client = new VapiClient({ token: "your-api-key" });
const call = await client.calls.get("019ac00d-e0a2-7dd8-8f66-bd69662339bc");
console.log("Recording URL:", call.recordingUrl);
console.log("Transcript:", call.transcript);

import { VapiClient } from "@vapi-ai/server-sdk";
const client = new VapiClient({ token: "your-api-key" });
const call = await client.calls.get("019ac00d-e0a2-7dd8-8f66-bd69662339bc");
console.log("Recording URL:", call.recordingUrl);
console.log("Transcript:", call.transcript);

This will fetch the recording and transcript if they are available for your call. For more details, see the Vapi Call Recording documentation.

Source:

Call recording

⤵️ Mention @Vapi Support Bot for follow-ups 🐥

KyleAPP•11/28/25, 12:50 AM

Hi Amin VZ,

It looks like you might be experiencing the error code call.in-progress.error-vapifault-worker-not-availablecall.in-progress.error-vapifault-worker-not-available. This error indicates that the worker responsible for managing your call was not available at the time needed. Typically, this could result from server issues or resource limitations.

Here’s what you can do:

Check Resource Limits
- Ensure that all resource quotas and limits are adequate for your current call volume.
Server Health
- Verify that your server is operating normally and not facing any downtime or performance bottlenecks.
Review Logs
- Check your logs for any additional details that might point to the root cause of the worker availability issue.

For more detailed troubleshooting steps or configurations, you can refer to the Client Message Documentation.

Let me know if you need more help.

yucky-goldOP•11/28/25, 10:11 AM

Can this be related to that I actually did publish a new version of the assistant while this call was happening? I updated the call-timeout time.

yucky-goldOP•11/28/25, 10:11 AM

KyleAPP•12/1/25, 10:39 PM

Yes, updating your assistant during an active call could definitely cause issues with the call's behavior.

yucky-goldOP•12/2/25, 10:37 AM

Ok. Perhaps a check when it is done, if there is an ongoing call. atleast a warning that it might effect ongoing calls ð

KyleAPP•12/4/25, 6:37 AM

Thanks for the feedback. Most of the time, it wont cause an error since the configuration is set and unable to be changed once the call starts. Even when the worker dies, it will still have some recording and transcript available in the logs. Just be sure to check the call logs page for that id.

import { VapiClient } from "@vapi-ai/server-sdk"; const client = new VapiClient({ token: "your-api-key" }); const call = await client.calls.get("019ac00d-e0a2-7dd8-8f66-bd69662339bc"); console.log("Recording URL:", call.recordingUrl); console.log("Transcript:", call.transcript);

call.in-progress.error-vapifault-worker-died

Similar Threads

Similar Threads

Similar Threads