Hello! I am having an issue where I am scheduling calls and they are not started. They continue to say "scheduled" even after the time has passed. I have had this issue before and the fix was to recent my concurrent lines. Org ID: 692d892a-5f2a-444f-9279-9b3080b577c2 Campaign ID: 6b3c977b-1fab-43d6-bf93-15fc9ea3a76c Example call ID within the campaign: 019c1f20-b3ad-7440-8a6f-49354d4bb00e https://cdn.discordapp.com/attachments/1467937577515487488/1467937577746038914/image.png?ex=698232e7&is=6980e167&hm=88139b290dedc6d7b963263fcd4d11858cb18724fc05e307415622b2d8a66e56&

Action Needed: Your outbound campaign calls may be stuck in "scheduled" status due to hitting your organization's concurrency limit. To resolve this, check your Vapi org's concurrency settings and increase the limit if possible: 1. Go to your Vapi Dashboard and review your current concurrency limit. 2. If needed, request an increase or reset from your admin or support. According to the documentation, only the allowed number of calls will start at once; the rest will queue until slots are free. See: [Vapi Outbound Campaigns Overview](https://docs.vapi.ai/outbound-campaigns/overview) Source: - [Vapi Outbound Campaigns Overview](https://docs.vapi.ai/outbound-campaigns/overview)

I would like a reset

Reset the concurrency. I just want to inform you delayed campaign is a known issue, it happens in peak loads, and a primary issue our team is working on. This should be fixed in Q1 itself.

Awesome thank you. Can we please keep this thread open and I can message you when this happens? It happens to me often

Sure, Threads are auto-closed after a few days, but you can always message in the ticket.

Hello, I am having the issue again. Please reset my concurrency lines. Campaign ID: 94fa0d7a-633c-444c-9a4c-08eb4ee949f7 Org ID: 692d892a-5f2a-444f-9279-9b3080b577c2

I think it's not concurrency line issue, as concurrency is not being stuck, can you describe what's the behavior you're seeing in these campaign?