Execution & History

This page explains how automation task executions are started, how run progress is shown, and how to investigate run results.

Where Executions Start

• Task configuration: use the Execute action for the selected automation task

• Published Tasks: authorized users can execute published tasks from the user-facing list

If a task has linked parameters, the execute dialog requests values before queuing the run.

Execution History View

In task history, each run appears as an expandable entry with key metadata and step-level results.

• Run timestamp, current status, and completed-step count

• Task-level variables captured during execution, including user input, system variables, and step output variables

• Step table with started/ended timestamps and per-step status

• Grouped step order, so parallel group behavior can be compared with actual start times

• Expandable step details for parameters, output, and error details

• Pagination for historical runs

Variables in History

History shows the variables that belonged to a specific run. This is often the fastest way to confirm that a value was created before a later step tried to use it.

• Linked parameter values are captured when the run starts

• Certificate task variables are captured when certificate context is available

• Script and integration output variables are added as producing steps complete

• Variable marker lines from scripts are stored as variables, not as visible step output

If a later step did not receive an expected value, check the producing step status, the variable list for the run, and whether the steps ran sequentially or in parallel.