Delay

The Delay node Individual components that make up a runbook automation, each performing a specific function such as data queries, transformations, logic, integrations, or visualizations. pauses the current branch of a runbook An automated workflow that executes a series of steps or tasks in response to a triggered event, such as the detection of anomalous behavior generating an incident, a lifecycle event, or a manually executed runbook. or subflow for a specified number of seconds, then continues to the next node. Use the Delay node when a later step should wait, for example to give an external system time to apply a change before you query it again.

The Delay node must have exactly one parent. The editor reports an error if the node has no parent or more than one parent.

The Delay node does not produce visualization data. You cannot wire the Delay node into a visualization, impact, trigger, or comment node. Downstream processing nodes can continue after the pause.

Duration limits

When you type a duration, the value must be a positive integer from 1 through 3599 seconds (just under one hour). The editor default is 30 seconds. Values of 0, negative numbers, and 3600 seconds or greater are not invalid.

You can place a Delay node inside a subflow A reusable automation chunk that performs frequently used functions, such as opening a ticket in an external system, and can be used to implement integrations with third-party systems. and run that subflow from an Iteration node when you need a longer wait built from repeated shorter pauses.

Properties

Node Label: Type an informative name for the Delay node. You can keep the system-provided default of Delay if you wish.

Delay (Seconds): Choose how to set the pause, then supply the duration.

• Enter The Delay: Type the number of seconds to wait. The value must be a positive integer from 1 through 3599.

• From Variable: Select an integer variable An entity type representing software applications deployed in the customer environment that are monitored for performance and anomalies.. Runtime integer variables appear first. In Incident and Lifecycle runbooks, integer incident variables appear after the runtime variables. The list includes only integer variables. If the selected variable no longer exists, the editor reports that the variable is not valid.

Debug: Select Debug if you want to receive debug data when the node executes.

Runbook compatibility

You can use the Delay node in the following runbook types:

Incident, Lifecycle, On-Demand, External (Webhook), and Subflow.