The Delay node enables you to pause a flow before proceeding to the next node. You can configure it to wait for a specific duration or until a certain date and time.
To name a few, you can use a delay node in scenarios where you need to send reminders about an event at regular intervals, retry connecting to a server.
Double-click the node to configure it. You can configure the delay node using either Delay time or Wait for date options.
Configure the delay settings:
- Delay time - the duration for which the flow execution needs to be delayed
- Time out (in seconds) - delay duration in seconds.
- Wait for date - the date till which the flow execution needs to be paused. Specify the date-time in the dd-mm-yyyy hh:mm:ss format. The platform automatically detects the server timezone.
Please note that when you configure 'x' seconds of delay using the delay node, the processing is delayed by at least 'x' seconds. It can sometimes be higher depending on the number of active flow execution sessions across all services within your tenant.
You can see a list of all the flow variables available for use within this node under the Input Variables pane. You can also search for a variable using the Search field.
You can see the list of variables that you explicitly create and configure for this node under the Custom Variables pane. You can also add a custom variable to the flow using the Add New Custom Variable button. For more information, see Custom Variables.
You can see the data that this node generates as output variables. These variables are available for use in subsequent nodes. The following are the standard output variables for the delay node:
- delay.waitTime - contains the time duration for which the flow waits.
You can see the list of possible node outcomes for this node under this pane. You can customize the node labels using the Edit (pencil) icon. The node exits through one of the node edges corresponding to the outcome of the node.
|* onTimeout - the flow exits through this node outcome when the specified timeout duration is completed
|* onError - the flow exits through this node outcome when there is an error due to invalid input
Use this tab to configure the transition actions for
On-leave events. However, configuring transition actions is optional. For detailed instructions about configuring the transition actions, see Node Transition Actions.
A user loses connection to the email server. Before attempting to reconnect to the server, you can configure the flow such that there is a delay of 10 seconds.
Updated 3 months ago