Use Delay to pause a workflow before its next action. For example, after a purchase request is approved, wait three days before sending a follow-up to the receiving team.
Add a Delay Action
In the workflow designer, open Logic and flow.
Drag Delay onto the canvas. Connect the step that leads into it and the step that should run after the wait.
Select the action and open its settings.
Configure the Delay Action
Choose when the workflow should resume, then fill in the settings for that delay type.
Action name
Enter a name that explains the wait, such as Wait three days before following up.
Delay type
Delay for a set amount of time waits for a duration measured from when the workflow reaches the action.
Delay until a date waits until a date and time entered in the action or supplied by workflow data.
Delay until the condition meet waits for a condition to become true.
Delay for a Set Amount of Time
Use a duration when the timing is relative to the workflow's progress. Start counting from the action's arrival time. For example, if the workflow reaches Delay after approval, a three-day delay is measured from that point.
Configuration fields
Count is the number of units to wait. Enter a fixed number or choose the expression editor to derive the number from a workflow variable, form field, or calculation.
Unit is Month, Week, Day, Hour, Minute, or Second.
Example scenarios
Set Count to 3 and Unit to Day for a follow-up three days after the node is reached. If the wait depends on a request's priority, use a numeric expression for Count and test requests that return different counts.
Delay Until a Date
Set Source of delay to Specific time for an entered date and time or Dynamic time for a date and time derived from workflow data.
A. Specific time
Select the target calendar Date and Time of day.
Note: The maximum delay duration is 1,096 days.
For example, choose the date of a planned inventory check and set the time to 16:00.
B. Dynamic time
In Date and time, open the expression editor and choose a date or date-time value from the workflow, form, or a calculation. For example, use Expected Delivery Date so different requests can resume at different times. Test the values you expect to receive, including a blank date or a date that has already passed if either can occur in the workflow.
Delay Until the Condition Meet
Use this option when the workflow should continue after a configured condition becomes true.
Configuration fields
Open Condition editor and build the condition using data available to the action. In a test run, begin with the condition false, then change the relevant value. Check that the connected action starts after the condition is met.
Example scenarios
Wait for a payment status to become Completed before creating a follow-up task. Test with a record whose status changes and one whose status stays the same, and check that the second run remains at the wait during the test.
Best Practices
Save and publish the workflow in a test application. For a duration, start with a short test such as one minute. For a date, choose a near-future time and check that the workflow resumes at the time you intended.
Use a test recipient or a test record for a subsequent email or data change. Consider how many runs can be pending at once before introducing a long wait into a frequently used workflow.
Summary
In Workflow instances, look up the test run by its tracking number. Review its logs and compare the observed follow-up time with the time you expected. View and manage workflow instances

