Hi, my account concurrency counter is stuck at -1 remaining with zero active, queued or scheduled calls. Verified via API all 3,700 calls show status: ended. On PAYG plan with 10 concurrency. Counter never reset after a batch run earlier today. Org ID: 9d9772f3-9eb6-4d88-a410-1b90f2fd7280 can someone reset it? https://cdn.discordapp.com/attachments/1502033924627628052/1502033924774297731/Screenshot_2026-05-07_224441.png?ex=69fe3d9a&is=69fcec1a&hm=6f8e090471a4b0f7d2ee2bf2015ba4e5f3cb0597ac94deebea8d87df09ce9285&

Your concurrency counter being stuck at -1 is an account-level issue that requires support intervention. To resolve this quickly, report the problem to Vapi support with the following details: - Organization ID: 9d9772f3-9eb6-4d88-a410-1b90f2fd7280 - Issue description: Concurrency counter stuck at -1, no active/queued calls, cannot make new calls - Screenshot or error message: (attach your image) Submit your report at [Vapi Support](https://dashboard.vapi.ai/support) or via the dashboard. This ensures the support team can reset your concurrency counter promptly. Sources: - [Vapi Call Concurrency Documentation](https://docs.vapi.ai/calls/call-concurrency) - [Vapi Issue Reporting Guide](https://docs.vapi.ai/issue-reporting)

Hi Mango, I have reset your concurrency. Please check and let me know if you need any help.

Hey Praveen quick question about POST /campaign behavior. I’m creating a campaign without schedulePlan (just name, assistantId, phoneNumberId, customers), but the campaign’s calls are still being created with a schedulePlan and end up in status: scheduled instead of starting immediately. Example call shows: schedulePlan.earliestAt ≈ +2 minutes after creation and latestAt ≈ +24 hours later. Is there a way/flag to make campaign calls start immediately (no schedule window),

When a campaign is created, the system immediately tries to start each call. If it hits your account's concurrent call limit on the very first attempt, it automatically injects a schedulePlan for the remaining calls in the batch - which is why you're seeing earliestAt ≈ +2 minutes and latestAt ≈ +24 hours even though you didn't pass a schedulePlan in your request. It's a graceful degradation to ensure calls don't just fail silently.