You can review automation run traces to inspect the execution path of a workflow, read node-level outputs, and identify where a failure occurred. Use trace data to debug failed runs and verify successful execution outcomes.
Before you begin
- You have access to Automation Orchestrator with permissions to view workflow executions.
- At least one automation run has completed, failed, or been cancelled.
Procedure
- Locate the automation run in the run history.
In the Automation Orchestrator web console, click Workflow Runs.
Use the filters to locate the specific run by workflow name, execution status, or time range. Select the run you want to inspect.
- Open the consolidated trace view for the selected run.
Click the run entry to open the trace view. The trace view displays the complete execution path as a sequence of nodes, showing the order in which the workflow executed each step.
- Read node outputs to understand the execution results at each step.
For each node in the trace, review the following information:
- Node name — the descriptive label assigned to the node in the workflow canvas.
- Status — the execution result for this node.
- Input data — the data passed to the node when it started execution.
- Output data — the data produced by the node after execution completed.
- Timestamps — the start and end times for the node execution, which you can use to calculate duration.
Each node in the trace reports one of the following status values:
| Status |
Description |
| Success |
The node completed execution without errors and produced output data. |
| Failed |
The node encountered an error during execution. Review the error details for the failure reason. |
| Skipped |
The node was not executed because a conditional branch excluded it from the execution path. |
| In progress |
The node is currently executing. This status appears only for runs that are still active. |
- Identify the failure point in a failed run.
For runs with a terminal status of failed, locate the first node with a Failed status in the trace view. Click the failed node to expand its error details, which include:
- The error type and error message describing what went wrong
- The input data that was passed to the node, which you can use to reproduce the failure
- The timestamp of the failure, which you can correlate with operational logs for additional context
If the workflow has multiple failed nodes, the first failure in execution order is typically the root cause. Subsequent failures are often cascading effects of the initial failure.
Results
You have reviewed the automation run trace and identified the execution outcome for each node. For failed runs, you have identified the specific node where the failure occurred and read its error details.
If the failure requires further investigation, correlate the node timestamps with operational logs for infrastructure-level context. For operational log access, see View operational system logs for troubleshooting.