Hi Team, I'm experiencing issues when initiating calls in VAPI in batches. Some of the calls are created in VAPI but never start. Additionally, no logs or tool calls reach the backend through the webhook, so we can't determine what happened with those specific calls. Here are a few examples: https://dashboard.vapi.ai/calls/07d55090-0d93-4c5b-b6c6-c42d7839e3df https://dashboard.vapi.ai/calls/eaad1bd4-3e62-4a4b-b7b3-980cf93c20fe https://dashboard.vapi.ai/calls/9d92bf8e-ed4e-47bf-ab94-fb2e59ad521c Thanks!

Actionable Suggestion: Since some calls are created but never start and no webhook is triggered, the recommended next step is to report these call IDs to Vapi support for backend log investigation. You can do this by sending a structured report like:

text
Call ID: 07d55090-0d93-4c5b-b6c6-c42d7839e3df
Issue: Call created but never started, no webhook received
Expected: Call should start or at least trigger a webhook event

This allows the support team to check connection logs and provide targeted help. [Reference: Vapi Issue Reporting Guide](https://docs.vapi.ai/issue-reporting#copy-the-call-id) Sources: - [Vapi Issue Reporting Guide](https://docs.vapi.ai/issue-reporting#copy-the-call-id) - [Vapi outbound call not triggering (Discord)](https://discord.com/channels/1211482211119796234/1341449578100031488)

I have already mentioned the issue and call id links but here is also the orgid if needed fdef5a60-8a66-4d33-9c39-cf6d85baa4cb

same issue here

Are you getting this error: 'twilio-reported-customer-misdialed'

Any updates?

The error we are seeing for these calls is as shows:

🔵 14:28:04:771 Call `07d55090-0d93-4c5b-b6c6-c42d7839e3df` Waited 300s But Transport Never Connected.

The call is being started on our end and times out before the telephony provider responds back to the request. Please check any logs on the telephony side.

Thanks kyle, we are using twilio. Shouldnt vapi send us a status update through the webhook informing us of the timeout?

Same Issue here

If you have the call-status-update server message applied, there are only these types of statuses:

Status Events
scheduled: Call scheduled.
queued: Call queued.
ringing: The call is ringing.
in-progress: The call has started.
forwarding: The call is about to be forwarded.
ended: The call has ended.

Thanks for the response kyle

Yes, you are correct that failed calls and timed out calls will appear as

ended

. EndedReason will give you more details about what actually caused the call to end.