added the new error code call.start.error-vapifault-worker-not-available (#1267)

Author: stephenvapiai

fern/calls/call-ended-reason.mdx

@@ -61,6 +61,7 @@ These occur before the call connects, during resource setup.
 - `call.start.error-get-resources-validation` — The assistant, tools, or other resources failed validation.
 - `call.start.error-get-transport` — Error setting up the call transport (Twilio, Vonage, etc.).
 - `call.start.error-vapifault-database-error` — Internal database error during call setup. Retry or contact [support](/support).
+- `call.start.error-vapifault-worker-not-available` — The call's queue time expired before a call worker became available, so the call was not placed. Retry the call.
 
 ### Phone number limits
 

fern/calls/troubleshoot-call-errors.mdx

@@ -95,6 +95,7 @@ This guide explains errors by symptom. For a complete reference of every `endedR
     |---|---|---|
     | `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.start.error-vapifault-worker-not-available` | The queue time expired before a call worker became available; the call was not placed | Retry the call. This is a transient capacity issue. |
     | `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 |
   </Accordion>