Outbound campaign finished after 10 calls
# support
o
Hello, I just ran two outbound campaigns and both stopped after 10 calls with status 'completed'. When creating the campaign - and that was the behaviour over the last weeks - it was promised to queue the calls according to the pricing plan (see screenshot). I check the campaign via API retrospectively, and there were all 50 calls uploaded correctly. However, only 10 were executed. Two example campaign ids: - acc70b14-493f-4343-b633-ff17a8408ad1 - 81e768a6-e145-4cc1-b1db-7e9439f29956 Has VAPI a temporary issue, or what is the reason for the unexpected campaign stop? https://cdn.discordapp.com/attachments/1413135208332525600/1413135208848429158/Screenshot_2025-09-04_140849.jpg?ex=68bad438&is=68b982b8&hm=0aba062495a1e2eef5a5eea82fa0cf5891b40d718723672ab9eebabdcdd6758d& https://cdn.discordapp.com/attachments/1413135208332525600/1413135209574170684/Screenshot_2025-09-04_140929.jpg?ex=68bad438&is=68b982b8&hm=7848e308396f683d17db7bfae28931f80c63bdce022b79aa4e00a729b31d2851&
v
It looks like your campaigns stopped after 10 calls due to reaching your organization's concurrency limit. To allow more simultaneous calls, you can increase your concurrency limit by visiting the [Vapi billing page](https://dashboard.vapi.ai/org/billing) and selecting the appropriate add-on. Action: - Go to your billing dashboard and adjust the "Maximum Concurrent Calls" setting to match your campaign needs. This should enable future campaigns to process more calls in parallel as per your plan. Source: - [Changelog October 10, 2024](https://docs.vapi.ai/changelog/2024/10/10)
It appears your campaign stopped after 10 calls due to either a concurrency limit or a known intermittent issue where outbound calls do not trigger as expected. To help diagnose, please check if your concurrency settings match your plan and if any recent changes were made to SIP or webhook configurations. If the issue persists, contact Vapi support with your campaign IDs for further investigation. Tip: You can view and adjust your concurrency limits in your [Subscription settings](https://dashboard.vapi.ai/org/billing) if needed. Sources: - [Vapi outbound call not triggering (Discord)](https://discord.com/channels/1211482211119796234/1341449578100031488) - [Subscription schema and concurrency limits](https://docs.vapi.ai/changelog/2024/11/11)
c
Hi Oliver, If your outbound campaign finished after only 10 calls, it's likely related to your concurrency limit. This limit dictates the number of calls Vapi can process simultaneously. By default, the limit could be set to 10, meaning any additional calls would be queued until slots become available. To address this, you can request an increase in your Vapi organization's concurrency limit, allowing more calls to run concurrently. More details on managing these limits can be found in the [concurrency section of the Outbound Campaigns documentation](https://docs.vapi.ai/outbound-campaigns/overview). Also, ensure that your telephony provider's limitations align with these adjustments.
But the fix is for now. If there was a test on the 'daily' channel, it may stop working in the future again...
My concern is not about the 10 concurrent calls, I am fine to pay more to have more lines. But the queuing didn't work. So, the outbound campaign finished with status 'completed' after these 10 calls, and never tried the other calls laters.
So, as I expected. Since today it also stopped working on the 'weekly' channel. Another example campaign ID from today: 94c94540-fe7e-49ae-a168-95cabe20e919. Again, the campaign finishes with status 'completed' without queuing!
j
Having the same issue here, stops at 10 calls even though there are 700 entries in the file
c
Could you also please provide a screenshot of the campaign and the list of calls that did not execute? It seems unlikely that some of the 690 calls did not even attempt to retry unless there were some calls stuck in the queue that never initiated then just stopped trying
o
c
Thank you for providing this information. Our team is currently looking into this issue
3 Views