Hi Vapi, My Org ID is: d1f49a88-3e89-445c-b5df-4590fbab9ea6 I just launch an outbound campaign with ID: 364aced0-c936-4e41-90de-74650baa482c however, the majority of the calls got "queued" and they dont refresh. Normally, I hit my concurrency limit when I lunch a campaign like this and calls will be initiated as soon as the last call ends. In this case, only 20 calls were made and the rest is stucked. Can you help unlock this situation? Should I cancel the campaign and create a new one? Thanks for help, this is urgent!

Hi, It's a platform limitation when VAPI is under peak load, calls in campaigns may be delayed.

We are planning to fix this, mainly an infra issue. If your workflow is time-sensitive, then consider using /call endpoint to create a call, and automate with a custom workflow using n8n/ any other automation platform. This issue happened with scheduled calls only.

Ok, thanks for explanation. In order for me to proced, will you please delete any active/scheduled/queued call and reset my concurrency counter in my org ID: d1f49a88-3e89-445c-b5df-4590fbab9ea6 and org ID: dd9888e7-3297-495f-8d70-a14de5ef35ad ? This will allow me to deploy new campaigns tomorrow, ensuring all my concurrency channels are free.

I had a similar challenge, but with 1 line only.. always hitting the concurrency limit ont eh second call I wrote custom campaign manager to fix it.

Concurrency counter is now 0 for both d1f49a88-3e89-445c-b5df-4590fbab9ea6 and org ID: dd9888e7-3297-495f-8d70-a14de5ef35ad