Hi Vapi Support — I’m seeing outbound campaigns get “stuck” repeatedly (happened yesterday and again today, across two campaigns). CampaignId: 02d12af2-4771-4069-920a-2fbe3fd76ae2. The campaign starts and seems to stall around the first ~10 contacts, then resumes 40–50 minutes later. Evidence: in this campaign there are calls with createdAt ~17:02Z but startedAt ~17:48–17:53Z, e.g. 019e74b0-35d9-7000-abb7-9a6f46065e7b (createdAt 17:02:45Z, startedAt 17:48:44Z) and 019e74b0-4a65-7000-abc4-8318520681ab (createdAt 17:02:50Z, startedAt 17:53:34Z). AssistantId: c34cc301-ad31-466a-9bf1-7b89b7a4e66d. PhoneNumberId (Twilio): 4fefe6ec-b7d5-4023-9a7f-b7a12c02ad84 (number +15622739658). Also, on many calls I’m seeing twilioCallSid and twilioCallStatus come back empty. Can you help check if this is carrier/Vapi throttling, a concurrency/queue issue, or a transport tracking bug in the campaign runner?

Hey, This is a bug with the scheduler for campaigns. It sometimes gets stuck. We are currently working on a fix. Let me know if you face this issue again.