Delays in Zapify — Make an Action Wait

A delay makes an action wait before it runs, so an automation can pause between steps — add a tag now, email three days later, all in one automation rather than two. Delays are a Zapify PRO feature. This page explains how to add a delay, how the waiting actually works, why the wait is a floor rather than an exact moment, and how to remove one.

What is a delay?

A delay pauses an automation between steps, before an action runs. The trigger has already fired and any earlier actions have already run; the delay holds the next action for an amount of time you set. Add the tag, then email them three days later is one automation, not two.

Add a delay

Open the action's menu, choose Add a delay, and set an amount in minutes, hours, or days. The action then waits that long each time the automation runs.

How the waiting works

A delayed action is handed to Action Scheduler, the same queue WooCommerce uses for its own background work. When the time comes, the automation resumes from exactly the action that was waiting — the ones before it have already run, and the ones after it have not.

It is a floor, not a moment

Action Scheduler runs about once a minute, driven by WP-Cron. So a one-hour delay means not before one hour, not exactly at one hour. On a quiet site with no real cron, it can be considerably later, because WP-Cron only runs when somebody visits.

If delays matter to you, set up a real server cron and define DISABLE_WP_CRON. Zapify → Settings → System status says whether this is worth doing on your site.

Because of that, the shortest delay Zapify offers is one minute. Anything shorter would be a promise the queue cannot keep.

Removing a delay

Open the delay and choose Remove delay. The action goes back to running as soon as it can, and nothing else about it changes.

What a delay is not

A delay does not re-check the automation's conditions when it wakes up. The decision to run was made when the trigger fired; the delay only postpones the doing. If you need the condition checked at the later moment, put it on the delayed action itself — see filters and conditions.

Conclusion

Delays let one automation span time — act now, follow up later — by pausing before an action runs, and they rely on Action Scheduler so the wait is a floor rather than an exact clock. For deciding whether a step runs rather than when, see filters and conditions, or return to getting started to build an automation to delay.

FAQs

Are delays free in Zapify?

No. Delays are a Zapify PRO feature. The free build can react to triggers and run actions immediately, but it cannot pause an automation between steps. Upgrading to Zapify PRO unlocks the "Add a delay" option on any action, letting you set a wait of minutes, hours, or days before that step runs.

How accurate is a Zapify delay?

A delay is a floor, not an exact moment. Delayed actions run through Action Scheduler, which fires about once a minute via WP-Cron, so a one-hour delay means not before one hour. On a quiet site where WP-Cron only runs when someone visits, it can be later. Set up a real server cron and define DISABLE_WP_CRON for reliable timing.

What is the shortest delay Zapify allows?

One minute. Action Scheduler runs roughly once a minute, so any delay shorter than that would be a promise the queue cannot keep. If you need something to happen instantly, do not add a delay at all — the action runs as soon as the automation reaches it.

Does a delay re-check conditions when it wakes up?

No. A delay only postpones the action; it does not re-evaluate the automation's conditions when the wait ends. The decision to run was made when the trigger fired. If you need a condition checked at the later moment, put that condition on the delayed action itself so it is tested when the action actually runs.

Where do delayed actions run in the background?

Delayed actions are handed to Action Scheduler, the same background queue WooCommerce uses for its own tasks. When the wait ends, the automation resumes from exactly the action that was waiting — earlier actions have already run and later ones have not — so a delay pauses the automation in place rather than restarting it.