Workflow Process Nodes Table
The Workflow Process Nodes table displays the workflow process nodes, such as activities or robots, associated with the workflow process selected in the Workflow Processes table.
Each workflow process has multiple nodes defined in the template, but not all nodes are executing at the same time. As the workflow process executes, the nodes are initiated in the order established in the workflow template.
Expand nodes to view any associated activities and tasks.
Table Views
The following table views are available by default:
All
All nodes.
Completed
Completed nodes.
Open
Nodes that are currently executing or are in the Running state.
Orphaned
Orphaned nodes are missing their corresponding assignment node in the workflow template and cannot be initiated.
Overdue
Nodes that have passed their deadline or due date.
Stalled
Stalled nodes are nodes that fail to execute properly.
For more information on warning and error states, see Workflow Process Health Status.
Table Columns
The following table columns appear by default:
Name
The name of the workflow process node or activity.
State
The current state of the workflow process node. States can include Running, Executed, Aborted, Suspended, or Terminated.
Deadline
The date by which the activity must be completed.
Date Started
The date the node entered the Running state.
Date Completed
The date the node completed.
Queue Name
This column displays the queue name that represents the workflow process node, which is useful to your system administrator in diagnosing site-level reasons for stalled workflow processes.
* 
This column is only available when using the Stalled table view.
Table Actions
You can use the following actions to investigate and resolve warnings and errors:
Delete orphaned tasks
Removes orphaned activities.
Complete
This action is available from the right-click actions menu of a node that has associated activities.
Select this action to complete all activities associated with the node. A confirmation message appears.
Restart Activity
Begins a stalled activity again by resubmitting the queue entry.
Before using this action, externalize the workflow template and repair the expressions for the problem activities.
Was this helpful?