1. A workflow can pause partway and continue later. This video shows the three ways it waits, and when to use each.
Actions

Workflows that wait

How a run pauses partway, and what lets it continue.

Draft a refund reply that follows the Returns policy.
Sam checks refunds over €100.
Send the approved reply to the customer.
  1. When a job finishes, its event starts the next job.
  2. A waiting job prepares its event, then holds it, so nothing after it runs yet.
  3. Three actions work this way. A set time, a matching event, or a person ends the wait.

Each event starts the next job

A waiting job holds its event

Three ways a wait ends

Draft the reply
LLM Call
Waiting job
Holds its event
Send the reply
Gmail · Send Email
Reply drafted Reply drafted
Prepares the event, then holds it
Waits for that event
Delay
A set time
Wait for Event
A matching event
Human Approval
A person
  1. Maya asks for a refund on order 4821, and a model drafts the reply.
  2. Refunds up to 100 euros are approved automatically. Hers is 180 euros, so Human approval holds the reply for Sam.
  3. While a job waits, the canvas and Logs show what it waits for. Here, Waiting for approval.

A model drafts the reply

Large refunds wait for Sam

It shows Waiting for approval

Email received
Draft a refund reply that follows the Returns policy.
Sam checks refunds over €100.
Send the approved reply to the customer.
Refund request
Maya Chen · order 4821 · €180
Auto-Approval Conditions
Approve without a person up to €100 €180 · waits for Sam
LogsLive Feed
26 Oct 2026, 10:22:41Triggered run Waiting for approval
  1. Sam opens Approvals. The instructions show Maya's order and amount.
  2. Under Output Event Properties, he reads the proposed reply and edits it.
  3. Approve publishes the event with his edits, and the next job sends the email. Reject ends the job, and nothing is sent.
  4. Sam can also decide the same request from the waiting job in Logs.

Sam decides in Approvals

He can edit the proposed values

Approve or Reject

Or decide it from Logs

Approvals
PendingAllApprovedRejectedExpired
PendingApproved 2 minutes ago
Instructions Maya Chen asks for a €180 refund on order 4821. Check the reply before it is sent.
Output Event Properties
{ "recipient": "maya.chen@example.com", "reply": "Hi Maya, your €180 refund for order 4821 is approved. It reaches your account within five working days." }
Reject Approve
Approved Workflow execution will continue.
Reject ends the job as Rejected
The email is not sent
Logs Run resultsWaiting for approval26 Oct 2026, 10:22:41
Steps
Draft the refund reply10:22:43Succeeded
Check large refunds10:22:44Waiting for approval
Check large refunds
ExecutionInput & outputCost
Pending Approval
PendingApproved2 minutes ago
Instructions Maya Chen asks for a €180 refund on order 4821. Check the reply before it is sent.
Output Event Properties
RejectApprove
  1. After the reply goes out, Delay holds its event for two days, or until a set weekday and time.
  2. Then the workflow asks Maya if her refund arrived, and Wait for event holds the run until she answers.
  3. It listens for a matching event, here an email from Maya. Email from other customers does not count.
  4. Every wait has a deadline of up to 30 days. This one gives Maya one day.
  5. When the deadline passes, the job fails, or continues with an expired result. Here, a later job then tells Sam she has not replied.

Delay holds it for a set time

Wait for event holds it for a reply

Only a matching event ends it

Every wait has a deadline

When the deadline passes

  1. A test from Run workflow approves every Human approval job automatically, so nobody is asked.
  2. In a test, Publish Events is off by default, so Delay and Wait for event skip the wait and continue at once.
  3. A passing test checks the later jobs, but no person approved anything.

A test approves on its own

Waits are skipped in a test

What a passing test checks

You're in draft mode, only read permissions are on by default
PermissionsChoose what this run is allowed to do for real. Change event
ReadNothing here reads from your connected integrations.
WriteGmail · Send EmailSlack · Send Message
Publish Events Each step publishes an event that other jobs and workflows can listen for. Wait two days and Wait for Maya's reply wait for the event when this is on, and are skipped when off.
Auto-approved A test run never waits for a person Check large refunds
Run workflow Logs
Test resultsSucceeded
Steps
Draft the refund reply10:31:05Succeeded
Check large refunds10:31:06Succeeded
Send the reply10:31:07Succeeded
Wait two days10:31:07Succeeded
Ask about the refund10:31:08Succeeded
Wait for Maya's reply10:31:08Succeeded
Auto-approved
Delay skipped
Wait skipped
The jobs after each wait run and pass
No person approved the refund
  1. Use Delay when the next step depends on time.
  2. Use Wait for event when it depends on a reply or another event, and set a deadline.
  3. Use Human approval right before a step that needs a person's yes. It cannot undo a step that already ran.
  4. You can now tell why a run is waiting. The docs pages Delay, Wait for event, Human approval and Approvals cover every setting.

When to use each

Delay
The next step depends on time
Follow up two days after the reply, or on Tuesday at 09:00
Waiting for delay
Wait for Event
It depends on a reply or another event
Maya's reply, with a one-day deadline
Waiting for event
Human Approval
It needs a person's yes
Refunds over €100, checked by Sam
Place it before the step that acts
ApprovalSend Email
Waiting for approval
Go deeper in the docs Delay Wait for event Human approval Approvals