Refer to the following page for a summary of all Workflow Nodes: RSA Governance & Lifecycle Workflow Nodes Summary.

Product Area: Workflows

Workflow Node: Stop

Applies to Workflow Types: All (Requests, Reviews, Rules)

Time to apply: <5 minutes

Impact: High — the Stop Node formally ends the workflow execution. It ensures no further processing occurs beyond this point and confirms successful (or unsuccessful) completion of the process.

Purpose: 

Stop Node is the stop delimiter for a workflow. It defines the end point of the workflow process — the stage where all workflow actions are complete, and the workflow instance is terminated. 

Summary: 

The Stop Node represents the termination point of a workflow. Once the workflow logic has completed all its approvals, activities, fulfillment, decisions, and subprocesses, control reaches the Stop Node — signaling the workflow has finished processing. This node ensures the workflow instance closes properly and all related runtime resources are released.
Stop Nodes are essential for maintaining workflow integrity, preventing loops or unintentional infinite processing.

Key use:

To cleanly terminate workflow execution and mark the process as complete.

Usage:

Every workflow must include at least one Stop Node to mark its end.

• Use Stop Nodes after all key processing or exception-handling logic is complete.
• Ensures the workflow terminates correctly and releases resources

General Notes/Benefits:

• Stop Nodes are easy to configure.

• Useful for tracking how the workflow terminates.

Configuration:

Stop node can be found under the Template Toolbar, in the Standard section on the left side panel. To add a new node to your workflow, click the desired node icon in the left panel, then double-click anywhere in the main workspace to place it.