ConvertKit automation wait steps: when delays drift and how to fix them

The newsletter for newsletter operators

Daily field notes on deliverability, AI tools, hosting, and monetisation. No "top 10 plugins" filler — real tools, real numbers, real failures.

ConvertKit automations let you insert wait steps between actions—pause three days, then send an email; wait until next Tuesday at 9 a.m., then tag a subscriber. Simple in theory. In practice, those waits don’t always fire at the moment you configured, and understanding why matters if you’re running time-sensitive sequences or coordinating sends across multiple automations.

Here’s how ConvertKit queues delays, where timing drift shows up, and how to design sequences that account for it.

How wait steps are queued

When a subscriber enters a wait step, ConvertKit calculates the target timestamp and places them in a queue. The platform checks that queue periodically—typically every few minutes—and processes any subscribers whose wait period has ended.

That means a three-day wait won’t fire exactly 72 hours later. If the queue runs every five minutes and your wait expires at 2:03 p.m., the subscriber moves forward at 2:05 p.m. For most sequences, that two-minute variance is invisible. But if you’re chaining multiple short waits or coordinating automation sends with broadcast emails, those minutes add up.

ConvertKit’s own documentation (checked November 2026) describes automation processing as “near real-time,” not instant. The platform doesn’t publish the exact polling interval, but operator reports and support threads suggest five-to-ten-minute windows are typical during normal load.

Where drift becomes visible

Three scenarios expose timing drift:

Chained short waits. If you stack multiple one-hour or 30-minute waits in a row—say, to drip five lessons over a single day—each step adds a few minutes of lag. By the fifth email, your 9 a.m. start has drifted to 9:40 a.m. or later.

Time-of-day waits during high-traffic hours. ConvertKit lets you set a wait until a specific time—”wait until tomorrow at 8 a.m.” If thousands of subscribers hit that same timestamp, the queue lengthens and processing slows. Emails that should land at 8:00 a.m. may trickle out until 8:15 a.m. or beyond.

Coordination with broadcasts. If you send a broadcast at 10 a.m. and an automation email is queued to follow 30 minutes later, drift can reverse the order. The automation might land at 10:28 a.m., the broadcast at 10:32 a.m., and your message sequence breaks.

How to design around it

Use longer waits when precision doesn’t matter. A three-day or one-week pause absorbs a few minutes of drift without issue. Reserve time-of-day waits for sequences where the hour matters more than the exact minute.

When you need tight coordination, collapse multiple short waits into a single longer one. Instead of three one-hour waits, use one three-hour wait. Fewer queue events mean less cumulative lag.

If you’re running parallel automations that need to stay in sync—say, a welcome sequence and a separate product-education track—don’t rely on matching wait durations. Use a shared event as the trigger instead. Tag the subscriber at a specific milestone and have both automations respond to that tag. The event timestamp becomes your synchronisation point, not a wait step.

For sequences where send order is critical, avoid mixing broadcasts and automation emails in the same window. If you send a broadcast Monday morning, don’t schedule an automation send for Monday afternoon. Push the automation to Tuesday or move the broadcast to Sunday. Build in buffer.

When to escalate

If waits consistently drift beyond ten minutes, or subscribers get stuck in a wait step and never progress, that’s not normal queue lag—that’s a processing issue. Check ConvertKit’s status page first, then reach out to support with the automation ID and specific subscriber examples. The platform logs each step transition, and support can trace where the delay occurred.

Most timing issues come down to design, not bugs. ConvertKit’s queue system works reliably for the majority of use cases, but it’s built for email marketing cadence—days and weeks, not minutes and hours. If your business model requires sub-minute precision, you’re pushing beyond what the platform’s architecture is optimised for.

Want more automation deep-dives? Reply with the platform feature you’re wrestling with, and we’ll add it to the queue.

The newsletter for newsletter operators

Daily field notes on deliverability, AI tools, hosting, and monetisation. No "top 10 plugins" filler — real tools, real numbers, real failures.

Other newsletters you might like

Irish Rugby Fans

The best Irish rugby updates, straight to your inbox — Six Nations, the Nations Championship and the provinces. Only when there's something worth reading.

Subscribe

Love California

Love California — in your inbox The Pacific Coast Highway, national parks, beaches, wine country and the best places to visit in California. One short email, every day.

Subscribe

Springbokfans

The best Springbok updates, straight to your inbox. Only when something worth reading actually happens.

Subscribe

Love Spain

Love Spain — in your inbox. Iconic cities, hidden pueblos and the best places to visit in Spain. One short email, every day.

Subscribe

Newsletters via the One Two Three Send network.  ·  Want your newsletter featured here? Click here