Execution Data

{"URL":["/*.*/awa/pm_executions"],"heroDescriptionIdentifier":"ice_ExecutionData","customCards":[{"id":"ice_TypesOfExecDataLists","title":"Types of Execution Lists","type":"customize","languages":["en-us"]},{"id":"ice_GenAIExecutionLists","title":"Analyzing Executions with Gen AI","type":"customize","url":"https://docs.automic.com/documentation/webhelp/english/ALL/components/DOCU/*.*/Automic%20Automation%20Guides/Content/_GenAI/GenAI_Overview.htm","languages":["en-us"]},{"id":"ice_UnderstandingExecDataLists","title":"Understanding the Execution Lists","type":"customize","languages":["en-us"]},{"id":"ice_TroubleshootingAndRootCauseAnalysis","title":"Troubleshooting, Root-Cause Analysis and Remediation","type":"customize","url":"https://docs.automic.com/documentation/webhelp/english/ALL/components/DOCU/*.*/Automic%20Automation%20Guides/Content/AWA/ProcMonitoring/PM_TroubleshootingRootCauseAnalysis.htm","languages":["en-us"]},{"id":"ice_RelnfoExecData","title":"Related Information","type":"customize","languages":["en-us"]}]}

When a task is executed, the information about that particular execution (type of task, runID, status, start time, end time, and so on) is stored. Executions lists provide a historical perspective over all the past executions of a particular task. For example, if a task has been executed 10 times, the Executions list of that task contains 10 rows, one per execution. By default, the most recent execution is displayed at the top of the list. Recording the execution data is triggered as soon as an object is activated and ends when the execution is completed. All Executions lists display real-time data at the time of execution, that is, they reflect any modifications to the task or underlying object. The Executions lists are a key audit feature that guarantees full audit capability. Together with the reports, they are the starting point to troubleshoot and perform root-cause analysis when tasks do not end as expected.

The Executions lists are available for all executable objects, Agents, Clients, Queues and Automation Engine processes (WPs, JWPs, CPs, JCPs, REST, PWP). Right-clicking a record in an Executions list opens a context-menu with the functions available for the selected task execution. You access the Executions list by right-clicking any object, task or execution and selecting either Execution Lists or Monitoring > Executions, depending on where you are.

Automic Automation's Gen AI is accessible from all Executions lists; use it to gain insights into a particular execution, get a summary of the object configuration and an explanation of how the execution went. You can ask questions and continue the conversation about the execution or any other related topic until you are happy with the results. For more information, see Analyzing Executions with Automic Automation's Gen AI.

Important! To be able to see these lists, your user definition must have the S - Executions authorization.

Notes:

The system keeps the execution data until explicitly removed from the database.
You can customize the number of entries that should be displayed in the Executions lists. See Defining the Default Number of Displayed Executions.

This page includes the following:

Types of Execution Lists

The following types of execution lists are available:

Executions

Available for tasks that are processed individually.
Child Task Executions

Tasks such as Workflows (JOBP), Groups (JOBG) or Schedules (JSCH) trigger the execution of other tasks (their children). The Child Task Executions is available for parents tasks and provides data on the execution of their children for a particular run.

Note: Automatic file transfers that store the external reports in the Automation Engine are child objects.
Parent Task Executions

Available for child tasks, these list provide data on the execution of both the parent and all its children.
Activator Executions

The activator is the instance that triggers the execution of a task. In the case of parent/child tasks, the activator of the child is usually the parent, but it must not always be so. If the child task is executed manually, for example, the activator is the user who triggered it.

Understanding the Columns in Execution Lists

All execution lists of executable objects display the same columns. Some columns are hidden by default. For more information about how to display hidden columns, see Working with Tables in AWI.

The following columns are displayed by default:

Name: Object name or alias (if available), see Name, Title, and Alias.
Type: Type of task, see Understanding the Object Types in Automic Automation.
Parent: RunID of the parent task, if available.
Status: Current status of the task, see Task Status
Activation Time: Date and time when the task was activated.
Start Time: Date and time when the task started generating.
End Time: Date and time when the task ended.

The following columns are also available:

Description:
Users: User names of the task owners separated by a slash: Owner/Owner. Task owners have either executed the task or actively assume ownership of the task.
Runtime: Duration of the execution.
Agent: Agent on which the task was executed.
Return Code: See System Return Codes of Executable Objects.
Queue: See Queue (QUEUE).
User ID:
Internal Account: Freely definable text assigned to the source object upon definition. You can use this text to perform searches and filter objects and tasks. See Defining the General Page.
Archive Key 1 and Archive Key 2: Freely definable keywords assigned to the source object. You can use them to perform searches and filter objects and tasks. See Defining the General Page.
Version: Every change made to an object creates a new version of that object. This column indicates the version of the object that was executed. See Defining the Version Management Page.
Modification Flag: Shows if the task has been modified at runtime and the name of the user who made the last modifications.
Process ID:
Remote Status: Available for SAP process chains and PeopleSoft Jobs, it indicates the status of the task in the target system.

Working with the Executions Lists

Right-click an entry in any of the execution lists to open a context-menu with the functions that are available to that execution. The functions that you can perform depend on the type of task to which the entry refers and on the status of the execution. For more information, see Available Functions Depending on the Task Status.

The Show in Process Monitoring option is always available. It opens the list of Tasks in the Process Monitoring perspective. The list is filtered using the runID of the selected execution.

Status of Tasks in the Execution Lists

When a task is executing, it goes through four execution stages. During each stage multiple things happen. To mention but a few: PromptSets are read, Agent Groups and Variables are resolved, scripts are generated, a number of checks happen and actions are taken based on those checks, and so forth. This means that during its runtime, that is, as long as a task is Active, it goes through many statuses.

The execution lists do not display these intermediate statuses. If a task is still executing, the Status column displays Unknown, meaning that the task is in any of the possible intermediate statuses. If you open the Details pane for a task with an Unknown status, the Status field indicates Active. This lets you know that the task status is unknown because it is still executing.

For detailed information about what happens during each execution stage and the statuses of a task during each stage, see:

Execution List for Agents

Recording the data begins when the Agent starts and ends when it terminates. In addition, an entry is created with every log rotation. For more information, see Initiating Agent Log Rotation.

The Agent execution data is available in Client 0 only.

Execution List for Clients

Each row on the Client Executions list represents a session of the selected Client. Recording the data begins when the Client starts and ends when it terminates.

Execution List for Servers

Each row on the Server Executions list represents a connection to the server.