Subflow Debugging

Debugging capabilities have been enhanced for runbooks that use subflowsClosed 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., making it easier to troubleshoot issues that occur within subflow execution.

For an overview of runbook debugging features, see Runbook Debugging Features.

Subflow Debug Tree View

The Debug Runbook Flow dialog shows detailed information about nodesClosed Individual components that make up a runbook automation, each performing a specific function such as data queries, transformations, logic, integrations, or visualizations. that execute inside subflows. Instead of displaying raw runbook output, the UI creates a sanitized tree view that makes it easier to understand subflow execution:

  • Node labels as primary identifiers: Node labels are shown as the primary label in the tree view, making it easier to identify nodes.

  • Removed unnecessary fields: Technical details like node IDs are removed from the display to reduce clutter.

  • Human-readable timestamps: UNIX timestamps are converted to human-readable timestamps or execution duration.

  • Standard Inspect view: When you select a node within a subflow, the standard Inspect view (used for regular runbook nodes) is displayed, providing consistent debugging information across all node types.

Node Selection in Subflows

When viewing a subflow node in the Debug Runbook Flow dialog, you can select individual nodes from within the subflow. The node selection list is sorted by execution start time and includes:

  • An icon representing the node type (same icon used in the Runbook Editor).

  • The node label.

  • The execution status of the node.

  • The execution duration of the node.

When you select an internal node from this list, the dialog displays that node's details in the same way as for any node in the Debug Runbook Flow. The Config, Error, Inspect (when debug is enabled for that node), and Debug (when debug is enabled) tabs show the configuration, errors, and debug output for the selected subflow node. For more about viewing node details, see Debug Runbook Flow.