Wait pauses an automation workflow and resumes it automatically when the chosen time is reached. Use it to leave time between actions, such as sending a message and checking whether the customer responded.
This step is available in the automation workspace.
Set up the step
-
Add Wait from Control flow in the step picker.
-
Choose an option under Wait until.
-
Fill in the fields for that option using the reference below.
-
If you need a particular time, turn on Choose an exact time of day where available.
-
Enter Time of day in 24-hour format, such as
09:00, if you enabled it.
Wait options
|
Wait until |
Fields |
|---|---|
|
A duration has passed |
Enter a positive whole number under Wait for. Choose minutes, hours, days, weeks, or months under Unit. |
|
The next weekday |
Select one or more Weekdays. The workflow resumes at the earliest upcoming choice. |
|
The next day of the month |
Enter one or more Days of the month from 1 to 31, separated by commas. For example, |
|
A date-time from a variable |
Select the Date-time variable. Under Timing, choose exactly at, before, or after that date and time. For before or after, fill in Offset by and Unit. |
You can choose a time of day for waits in days, weeks, or months, for calendar choices, and for a date-time variable. It is not available for a duration in minutes or hours.
What to expect
The workflow keeps its progress while it waits, then continues with the next step. Wait does not produce an output variable. You can find paused runs under Analyse in the automation workspace.
A weekday or day-of-month choice uses midnight if you do not choose a time. Today counts if the chosen time is still ahead. In a shorter month, a day such as the 31st becomes the last day of that month.
For a date-time variable, the offset is applied first. A chosen time of day then replaces the time on that date. If the resulting time is already in the past, the workflow continues immediately.
In the debugger, Wait checks its configuration and continues immediately so you can inspect the remaining steps.
Technical reference
Calendar choices use the workflow run's time zone. The step has no separate time-zone setting. Minutes and hours measure elapsed time; days, weeks, and months preserve the local clock time across calendar changes.
Date-time values can include an explicit time-zone offset. Text values without an offset use the run's time zone. Check the source value and its time zone if a date-time wait resumes at an unexpected time.