Hi support, Today I had a customer complain about an outbound call that failed due to a Vapi "unkown error". The call occurred about an hour ago. Is there a Vapi outage / issue causing calls to fail due to unknown errors? Org ID: 6ff55087-48b0-4037-a2aa-d4984d63ea98 Call ID: 57c0a1e0-e5f3-49d4-9d12-0b86890d0cc5 Assistant ID: 983069a5-94be-4f06-81b8-92ed02b76d3d Impact: When the call connects to the contact, no assistant message is played (silence) and the call ends after 15 seconds. Please let me know if you need any additional info to debug. Is there anything I can do to prevent these failures in the future?

The call with ID 57c0a1e0-e5f3-49d4-9d12-0b86890d0cc5 failed due to a "job stalled more than allowable limit" error. This indicates that a worker process that was handling this call became unresponsive for too long, causing the job to be marked as stalled and subsequently failed. When examining the specific error pattern: \- The call connected to the contact \- No assistant message was played (silence) \- The call ended after 15 seconds This is not an systemic Vapi outage, but rather an isolated issue with this specific call. Here's why: \- The error message indicates a worker process issue rather than a service-wide problem \- The stalled job mechanism is a normal recovery feature in the queue system \- The system properly detected the stalled job and initiated recovery