orgId: a3b411ef-b949-4f06-8287-18b439453505 Cannot make calls via API, scheduling calls (with a 1hr+ window) returns OK but no call is ever made. Before this today we had multiple test calls to my phone but only 5 of the 7 calls I recieved have a call log withing Vapi UI. We have an external app we push end call reports to so I can clearly see all 7 calls there too. Creating a campaign also just resulted in the entire campaign (3dfde99b-2196-433e-a911-c9c20d3813aa) being stuck in "scheduled" and it won't run. Now when attempting to generate a call im getting "over concurrency" when according to the logs there's not been a call made for 5 hours. We still haven't been able to make a single call since yesterday tried another campaign (1886d76f-9664-4e46-9c3e-d6b752187df4) and still stuck in schedule, concurrency warning being flagged but no calls been made for almost 24hrs now . we managed to get this working again by purchasing 1 concurrency lane. however this isn't really viable as now we can only do one call at a time (contradicting our free 10 lanes included in pay as you go) It's broken once again. The paid concurrency lane is unusable now. campaign 3906f9f8-69ad-4f76-b836-a4159c4e417b is stuck in limbo once again and max concurrency error message has returned. (no calls for 12hrs+) made a new organisation and issue persists. campaigns are stuck in scheduled forever and concurrency errors hit, 0 calls made.

Thank you for the detailed description. To help diagnose why your campaigns and outbound calls are stuck and concurrency errors persist, could you please confirm if your webhook URLs for call status updates (such as "end-of-call-report") are currently accessible and correctly configured in your assistant or campaign settings? A misconfigured or unreachable webhook is a common cause for stuck queues and concurrency issues ([see documentation](https://docs.vapi.ai/calls/call-queue-management#configure-vapi-webhooks-for-call-tracking)). If possible, please also check if your Redis counters (e.g.,

vapi:queue:active_calls

) reflect the actual state. Let me know the result, and we can proceed with more targeted troubleshooting! Source: - [Call queue management with Twilio](https://docs.vapi.ai/calls/call-queue-management)

the end call report is present and works (for the few calls that get through) . Are the client messages required ?

We have reset the concurrency on your account and apologize for the inconvenience. Let us know if those calls get stuck in limbo again. Also client messages are not required.

hi it's happened again today. See 019a0ad1-d25b-7000-b461-7b8708be35b6 for example, it's been scheduled for lunch today around 0800 this morning but it never got attempted. And now when trying to fire a call to my number its saying over concurrency (no calls made for 6 hours). Is there something we're doing wrong ? We use scheduling for both campaigns and individual calls, as well as instant call requests and instant campaign requests. I hope this gives context.