Hi Vapi Support Team, I’m running into an issue with outbound campaigns where a large portion of calls remain in scheduled and the campaign appears to stop dispatching/dialing, even though it should continue as concurrency slots free up. Account / Environment Org ID: bed6fe1b-fa6e-4b90-8697-24846bfc7214 Assistant ID: dcaead53-ddd2-4835-be44-fe06ee9085c1 Concurrency configured around 5 concurrent calls Affected Campaigns Campaign ID: 43f40595-aff8-4d6a-8c04-e8efb6adc57f (name: “MIXED OS 5-26-26”) Campaign ID: ac6b2196-7167-4a30-98b8-829ff0c47a0d (Also saw similar behavior on campaign 3eb4430d-cfcc-4f61-b76e-9db827ee914d) Phone Number / Carrier PhoneNumber ID: 28a1c5bb-128e-4185-9f96-64be3b44a5c4 Provider: byo-phone-number Number: +441........ PhoneNumber ID: 95a92099-ddf3-4950-bd00-2d1b94be06a3 Provider: byo-phone-number Number: +385....... What I’m seeing Campaign counters show many calls as scheduled (e.g., for 43f... we saw ~scheduled 659, ended ~10, queued ~10, in-progress ~4). However, on the Dashboard Calls page I sometimes see no calls actually in-progress, and the remaining calls don’t seem to start. A “scheduled call” example: 019e64c7-13c8-711f-a758-0d1c07955b9a shows 0 call logs (not dispatched). It may also not exist as a real call record yet, suggesting the campaign is creating placeholders but dispatch is stalled/out-of-sync. Request Could you please investigate why these campaigns are not progressing from scheduled → queued → in-progress reliably, and whether there’s: a dispatcher stall, a campaign state/counter desync, or a BYO-number/carrier gating issue preventing dispatch? Thanks, Carl