Long-Running Automations: Handling Waits of Hours, Days or Weeks

A practical field guide from Automation Ace.

The short answer

Long-running automations wait hours, days, or weeks for something: an approval, a payment due date, a trial expiration, or the next step in a follow-up sequence. For waits up to about a month, Zapier's Delay works. Make's Sleep is only for seconds or minutes. For longer or event-dependent waits, use a durable engine (Cloudflare Workflows, Temporal, or Inngest) or a tracking table plus a scheduled job. Whatever you choose, always re-check conditions when the wait ends, because the world may have changed.

Part of the automation architecture playbook. Background: durable workflows explained.

Common long waits in business automation

• Approvals: waiting for a manager, client, or legal sign-off. See approval workflows.
• Payment terms: reminders at 7, 14, and 30 days. See invoice reminders.
• Trials and renewals: nudges before expiration. See renewal automation.
• Follow-up sequences: onboarding and nurture steps over weeks. See client onboarding.
• External events: waiting for a document to be signed or a shipment to arrive.

Waiting tools compared

Zapier Delay

Delay For, Delay Until, and Delay After Queue pause a Zap run, with a maximum of about one month. Each delayed run is held in Zapier, which is hard to see in bulk and awkward to cancel when circumstances change. Pair waits with a re-check step (“is the invoice still unpaid?”) and use Human in the Loop for approvals. For more, see the built-in tools overview.

Make Sleep

Make's Sleep module pauses a running scenario for up to 300 seconds, useful for rate limits and short pauses, not business waits. For longer waits in Make, store state in a data store and run a scheduled scenario, or trigger a later scenario by webhook. See Make error handling.

Durable engines: Cloudflare Workflows, Temporal, Inngest

• Cloudflare Workflows: step.sleep for fixed waits and step.waitForEvent to pause until an external event, with a timeout. See the Cloudflare Workflows guide.
• Temporal: durable timers and signals; workflows can wait for very long periods and react to signals mid-wait.
• Inngest: step.sleep, step.sleepUntil, and step.waitForEvent inside event-driven functions.
• Next Gen Zaps also add pause-and-resume inside Zapier; see what Next Gen Zaps can do.

The tracking-table approach

Instead of holding a run open, write each future action to a table with a due date, and let a scheduled job process due rows. It works in any tool, has no maximum wait, and makes every pending action visible and cancellable.

FOLLOW-UP TRACKING TABLE (Zapier Tables, Airtable, or a database)
id | record_id | step          | due_at (UTC)         | status   | attempts | last_error | updated_at
1  | INV-1043  | reminder_1    | 2026-10-08 15:00     | pending  | 0        |            | 2026-10-01
2  | INV-1043  | reminder_2    | 2026-10-15 15:00     | pending  | 0        |            | 2026-10-01
3  | TRIAL-881 | trial_ending  | 2026-10-12 09:00     | sent     | 1        |            | 2026-10-12

Scheduled job (hourly): find status = pending AND due_at <= now
  -> re-check the record is still eligible (not paid / not upgraded)
  -> do the action -> mark sent (or failed + attempts + 1)

Build it with Zapier Tables, Airtable, or a database, plus a scheduler like Cron Triggers. Log outcomes with a run log.

Design rules for long waits

1. Re-check before acting: the invoice may be paid, the trial upgraded, the deal lost.
2. Make waits visible and cancellable, with a status per pending item.
3. Store times in UTC and convert for business hours. See business-hours automations.
4. Give every event wait a timeout and a fallback action.
5. Make actions idempotent so a retry does not send two reminders.
6. Plan for changes mid-wait: if the sequence changes, decide what happens to items already waiting.

Frequently asked questions

How do I make an automation wait for days or weeks?

For waits up to about a month, Zapier Delay works. For longer or event-dependent waits, use a durable engine like Cloudflare Workflows, Temporal, or Inngest, or store due dates in a tracking table and process due rows with a scheduled job.

What is the maximum delay in Zapier?

Zapier's Delay steps can hold a run for up to about one month. For longer waits, use a tracking table with a scheduled Zap or a durable workflow engine.

How long can Make's Sleep module wait?

Up to 300 seconds. For longer waits in Make, store state in a data store and process it with a scheduled scenario or trigger a later scenario by webhook.

What is a tracking table for long-running automations?

A table of pending future actions with due dates and statuses. A scheduled job processes rows that are due, re-checks eligibility, performs the action, and updates the status, which makes waits visible, cancellable, and unlimited in length.

Why re-check conditions after a long wait?

Because circumstances change: an invoice may be paid or a trial upgraded. Re-checking prevents sending reminders or taking actions that are no longer appropriate.