Hi, I've noticed that my campaigns are not triggering, long after their scheduled time. An example is campaign_id=

f6b64f95-b48a-41ce-bf2e-7a71b5c8a615

, which was due to be scheduled at 11:16am GMT today. I ended up cancelling it at ~12:00 noon, as I was attempting to demo this to a customer, but it never worked. This isn't the first time that I've seen this happen, but it was the first time that was in real-time with a customer, so it looked very bad. Can you see what went wrong, and are there additional parameters that I need to make my customers aware of (e.g. a campaign will trigger within X hours of the scheduled start datetime?) My Org ID is

bbef089b-7bd1-4385-981a-8fec3b32ea36

I can help figure out why campaign f6b64f95-b48a-41ce-bf2e-7a71b5c8a615 didn’t trigger on time. Could you confirm if any delays, time zones, or segmentation rules were applied? Understanding this will let me pinpoint the issue and advise on what to communicate to customers about scheduling expectations. Would you like me to review the scheduling logs directly for your Org ID? @dan_quill

Hi - I'm creating these campaigns via the Vapi Python SDK, with the following `SchedulePlan`:

schedule_plan = SchedulePlan(
    earliest_at=datetime.datetime.now(datetime.timezone.utc) + datetime.timedelta(minutes=1),
    latest_at=datetime.datetime.now(datetime.timezone.utc) + datetime.timedelta(minutes=2),
)

Yes - please do review the scheduling logs. Thanks

Thanks for sharing the SchedulePlan. I’ll review the scheduling logs to see why the campaign didn’t trigger—short windows like 1–2 minutes can sometimes cause timing issues. We can discuss the findings privately and go over best practices, and I’m happy to hop on a quick call to walk through it in real-time. When would be a good time for you? @dan_quill