Executions

You can monitor, manage, and troubleshoot symphony executions on the Executions page.

The Executions page shows a list of all symphony executions, both past and in progress.

Each entry includes these elements:

  • Symphony Name
  • Version
  • Start Date/Time
  • End Date/Time
  • Duration
  • Status: In Progress, Completed, Failed, Timed Out, Stopped
  • Executor
  • Triggered via (displays Direct or Schedule values)
  • Execution ID

You can search the execution by Symphony Name and Executions ID.

You can filter the executions by these criteria:

  • Status
  • Triggered by: If you use the Triggered by filter, you can select from these two options Me or Another user. The Another user option opens the dialog window in which you specify the user name.
  • Triggered via: Execution triggered could be either Schedule or Direct.
  • Date range: You can choose the date range from the drop down menu or customize it.

You can sort the executions by their Start Date/Time, End Date/Time, or Symphony Name.

Tip: Use pagination controls to navigate between pages and set the number of records per page.

Execution Overview page

If you click on an execution, the Execution Overview page opens.

The Execution Overview page contains two tabs:

  • Execution Events: The tab shows the symphony Name, Flow, Activity, Start Date/Time, End Date/Time, Duration, Flow Execution ID. You can see a chronological timeline of orchestration steps. If you click on an activity available on the canvas, you can find the details such as activity details, activity variables, or messages. The tab supports both diagram and list views.
  • Execution Details: The tab shows Start Date/Time, End Date/Time, Duration, Timeout, Triggered via, Schedule ID, Status, Executor, and Execution ID of the Symphony. The tab also provides access to the Input Variables and the Output Variables tabs which values are displayed only when you select the Input and the Output check boxes in the Symphony variables while creating the symphony.

Switch construct in the execution monitoring

During the symphony execution, the Switch construct is displayed on the Execution Events tab as a distinct state, similar to the activities. You can trace decision points in the orchestration flow.

In the execution monitoring you can find this information:

  • The switch construct clearly indicates which of the configured branches has been executed on the Construct Conditions tab.
  • The executed branch is highlighted, so you can identify the decision that was made at runtime.
  • All non-executed conditional branches are displayed in the construct conditions and remain visible for reference.
  • If none of the defined conditions evaluates to true, the default branch is executed and shown accordingly.
  • The execution follows the first matching conditional branch. Once a branch condition evaluates to true, the subsequent branch conditions are not evaluated.

On the Execution Overview page, you can stop and resume an execution and check the details of the execution.

For more information, see Constructs.

Filter construct in the execution monitoring

During the symphony execution, the Filter construct is displayed on the Execution Events tab as a distinct state, similar to activities and the Switch construct. In the execution monitoring you can find this information:

  • The Filter construct displays the evaluation result:
    • Condition success: When the condition evaluates to true and the flow continues.
    • Condition failed: When the condition evaluates to false and the execution stops.
  • When the condition is true, the execution proceeds to the next activity.
  • When the condition is false, the Symphony execution is marked as Completed with status Condition failed, and no further activities are executed.

Wait construct in the execution monitoring

During the symphony execution, the wait construct is displayed on the Execution Events tab as a distinct state, similar to activities and other constructs. When the wait step is completed, the configured wait duration is displayed. The execution overlay for the wait construct includes two tabs:

  • Construct Details: Displays the name (as configured in the symphony) and the construct type.
  • Messages: Displays information about the wait status:
    • In Progress: The execution is currently paused, waiting for the configured duration to elapse.
    • Completed: The wait duration has elapsed and execution has continued to the next step.
    • Stopped: The symphony execution has been manually stopped during the wait period.
    • Timed out: The wait construct has timed out.

After the wait duration completes, the wait construct status changes to Completed and the execution automatically continues to the next step. The wait construct displays status tooltips similar to the other activities.