Execution Events Table


The Execution Events table supplies comprehensive information with reference to all executed events, including the running of workflows and tasks as well as the activation of triggers. This report is useful for gathering runtime information, such as which workflow or task ran, which condition object triggered its execution, when execution started/ended, whether it ran successfully or failed and total runtime duration (among others). This report supports exporting to multiple document types, column filtering, data grouping, sorting, filtering and more.

For complete instructions on how to use table reports, see Using Table Reports.

Related Topics

Data Sources

The Execution Events report displays data in a two-dimensional table. The bound data is arranged in columns and rows. Grid columns correspond to data fields in a data source, rows represent data records. The table below lists the available data sources along with a description.



Event ID

The unique identifier of the event that took place.

Construct ID

The unique identifier representing an object and all of its settings and properties.


The user defined name of the object that ran.


The type of object that ran (i.e. Workflow, Task, Process).


The complete path to the repository location of the object that ran.


The date/time when execution started.

Executed On

The agent where execution of the object took place. If the execution type is a workflow, this field is left blank.


The result of the execution (i.e. Running, Success, Failed, Aborted).

Result Text

A textual description of the execution result.


The user that manually ran the object (if the object was manually started). If the object started automatically based on a trigger, this field is left blank.

Transaction ID

The unique identifier referencing the atomic transaction that took place which generated the log record. An atomic transaction is an inseparable series of actions or operations that must either all occur, or nothing occurs.

Workflow Instance ID

The unique identifier of the workflow instance that ran.

Instance ID

The unique identifier of the object instance that ran. Each instance of an object that runs during workflow execution is assigned an instance ID. This provides a way to distinguish each execution of an object, even if the same object is ran simultaneously.


This report can be filtered by columns which represent the data source, by starting and ending execution date/time and by repository items. In addition, a Filter button is available for column filtering and a Filter Editor is available for comprehensive filtering.

filter Custom Date Range

To filter by a custom date range:

  1. In the Starting field, click the down arrow to display a calendar (as shown below) and select the desired starting month, day and time.


  1. Double-click a portion of the current date value to highlight the month, day, year or time and click the up or down arrow to modify the value up or down.

  2. Follow the above instructions to modify the Ending date field.

NOTE: Date range filtering only applies to Audit Events and Execution Events tables

Filter Columns

The Columns button allows you to filter the columns to be included in the report. Columns vary depending on the report.

  1. Click the Columns button. A drop-down list of available columns appear.

  2. Select the columns to include in the report and deselect the ones to omit (omitted columns are unchecked).

NOTE: The image above is used mainly as reference to show the location of the Columns button. The list of columns to filter vary for each table-based report.

Filter Column Data

The Filter button allows you to filter the data that appears for a certain column.

  1. Hover your mouse cursor over a column header and click the Filter button that appears.

  2. Select the column data to include in the report from the drop-down list.

NOTE: The image above is mainly used as reference to illustrate the location of the Filter button. The displayed data may not reflect the appropriate table.

Advanced Filtering

The Filter Editor allows users to build complex filter criteria with an unlimited number of filter conditions combined by logical operators. To invoke the Filter Editor, right-click any column header and select Filter Editor. The Filter Editor displays filter criteria as a tree structure, where nodes represent simple filter conditions. If the filter criteria consist of multiple filter conditions, the Filter Editor contains multiple nodes linked by logical operators.