Home Paris Now Platform Capabilities Now Platform capabilities Process Automation Designer Process definitions Process executions

Process executions

Process executions

A process execution is a single, runtime instance of a process definition. Process execution records provide runtime information about process definitions, such as the current state and input record.

A process execution represents a runtime execution of your process definition. Each time a process definition is triggered, Process Automation Designer automatically creates a record in the Process Executions [sys_pd_context] table.

To access the records for an In Progress process execution, navigate to Process Automation > Process Automation Administration > Active Processes. Alternatively, you can see the process executions for all processes that ran today by navigating to Process Automation > Process Automation Administration > Today's Executions.

Fields

By default, each process execution record contains the following information:

Table 1. Process Execution record fields
Field	Description
Name	Name of the process definition that triggered this process execution
Created	Date and time when the process definition triggered
Input Record	Table name and record number that triggered this process execution
State	Current status of the overall process execution. For more information, see Process execution states.

Process execution states

A process execution record can have one of the following states:


State	Description
Queued	The process definition triggered, but the system hasn't started running the process execution yet.
In Progress	The process definition triggered, and the process execution is currently running. One or more activities in the process definition have a state of Ready or In Progress.
Complete	The process definition triggered, and the process execution is done running. All activities in the process definition have a state of Skipped or Complete.
Error	The process definition triggered, but an activity has an Error state. Errors can occur when the action, subflow, or flow specified in the activity definition's automation plan fails to run.
Cancelled	A user with the admin or pd_admin role explicitly canceled the process execution, and the execution has stopped running.

Previous topic

Next topic

Release version

Process executions

Process executions

A process execution is a single, runtime instance of a process definition. Process execution records provide runtime information about process definitions, such as the current state and input record.

A process execution represents a runtime execution of your process definition. Each time a process definition is triggered, Process Automation Designer automatically creates a record in the Process Executions [sys_pd_context] table.

To access the records for an In Progress process execution, navigate to Process Automation > Process Automation Administration > Active Processes. Alternatively, you can see the process executions for all processes that ran today by navigating to Process Automation > Process Automation Administration > Today's Executions.

Fields

By default, each process execution record contains the following information:

Table 1. Process Execution record fields
Field	Description
Name	Name of the process definition that triggered this process execution
Created	Date and time when the process definition triggered
Input Record	Table name and record number that triggered this process execution
State	Current status of the overall process execution. For more information, see Process execution states.

Process execution states

A process execution record can have one of the following states:


State	Description
Queued	The process definition triggered, but the system hasn't started running the process execution yet.
In Progress	The process definition triggered, and the process execution is currently running. One or more activities in the process definition have a state of Ready or In Progress.
Complete	The process definition triggered, and the process execution is done running. All activities in the process definition have a state of Skipped or Complete.
Error	The process definition triggered, but an activity has an Error state. Errors can occur when the action, subflow, or flow specified in the activity definition's automation plan fails to run.
Cancelled	A user with the admin or pd_admin role explicitly canceled the process execution, and the execution has stopped running.