From 374f5585868fc6b68b0d7a48dced2c1808ea6e99 Mon Sep 17 00:00:00 2001 From: Mehayla <68716877+Mehayla@users.noreply.github.com> Date: Mon, 24 Aug 2026 07:13:34 -0500 Subject: [PATCH] docs(calls): clarify vapifault-worker-not-available vs status.vapi.ai and billing --- fern/calls/troubleshoot-call-errors.mdx | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/fern/calls/troubleshoot-call-errors.mdx b/fern/calls/troubleshoot-call-errors.mdx index 4a144cab6..f8c1e9411 100644 --- a/fern/calls/troubleshoot-call-errors.mdx +++ b/fern/calls/troubleshoot-call-errors.mdx @@ -93,12 +93,16 @@ This guide explains errors by symptom. For a complete reference of every `endedR | Error code | Meaning | Fix | |---|---|---| | `call.in-progress.error-vapifault-transport-never-connected` | Transport never connected | Retry. Contact [support](/support) if persistent. | - | `call.in-progress.error-vapifault-worker-not-available` | No call worker available | Retry. This is a transient capacity issue. | + | `call.in-progress.error-vapifault-worker-not-available` | No call worker available | Retry — this is almost always a brief, transient capacity blip. It can affect a specific region or a subset of orgs for a few minutes without crossing the threshold to be posted as an incident, so [status.vapi.ai](https://status.vapi.ai/) showing "operational" does not rule this out. | | `call.start.error-vapifault-database-error` | Internal database error | Retry. Contact [support](/support) if persistent. | | `call.start.error-get-org` | Error fetching organization | Verify your API key is correct | + +Seeing several `vapifault-worker-not-available` (or other `vapifault`-prefixed) failures in a short window, but no matching incident on [status.vapi.ai](https://status.vapi.ai/)? Short capacity blips can resolve before they cross Vapi's incident-reporting threshold, so the status page won't always show them. Retry first — most clear up within seconds. If the errors continue for more than a few minutes or span multiple calls, contact [support](/support) with the affected `call_id` values and the exact timestamps. These errors are not billed by default; if you were charged for a call that failed with a `vapifault` error, include the `call_id` so support can issue a credit. + + ## Phone rang but nobody answered **What the caller experiences:** The phone rings but nobody picks up, or they hear a busy signal. @@ -243,7 +247,7 @@ To prevent provider outages from killing your calls, configure fallback provider For response-class guidance and checks across Vapi, your SIP provider, and your SIP infrastructure, see [Troubleshoot SIP response codes](/advanced/sip/troubleshoot-sip-response-codes). -For a detailed transfer debugging walkthrough, see [Debug forwarding drops](/calls/troubleshoot-call-forwarding-drops). +For a detailed transfer debugging walkthrough, see [Debug forwarding drops](/phone-calling/in-call-control/transfer-calls/debug-forwarding-drops). ## Call ended normally @@ -253,7 +257,7 @@ These are not errors — they indicate the call ended as expected. |---|---|---| | `assistant-ended-call` | Assistant ended the call via a tool or function | Expected behavior | | `assistant-ended-call-after-message-spoken` | Assistant spoke its final message and ended | Expected behavior | -| `assistant-ended-call-with-hangup-task` | Assistant used a hangup workflow node | Expected behavior | +| `assistant-ended-call-with-hangup-task` | Assistant used a hangup task | Expected behavior | | `assistant-said-end-call-phrase` | Assistant said a configured end-call phrase | Check your end-call phrases if calls end too early | | `assistant-forwarded-call` | Assistant transferred the call | Expected behavior | | `customer-ended-call` | Customer hung up | Expected behavior | @@ -267,7 +271,7 @@ These are not errors — they indicate the call ended as expected. - **[Call end reasons](/calls/call-ended-reason):** Complete reference of every `endedReason` code. - **[Debugging voice agents](/debugging):** General debugging workflow using dashboard tools, logs, and test suites. -- **[Debug forwarding drops](/calls/troubleshoot-call-forwarding-drops):** Deep dive into transfer failures. +- **[Debug forwarding drops](/phone-calling/in-call-control/transfer-calls/debug-forwarding-drops):** Deep dive into transfer failures. - **[Troubleshoot SIP trunk errors](/advanced/sip/troubleshoot-sip-trunk-credential-errors):** Resolve SIP credential validation failures. - **[Troubleshoot SIP response codes](/advanced/sip/troubleshoot-sip-response-codes):** Identify where a SIP request failed and what to check next. - **[How to report issues](/issue-reporting):** Include your `call_id` and account email when contacting support.