Agentic Workflow Control Actions
Audience: Administrators, Developers, Solution Architects
Purpose: Complete reference for the Agentic Workflow control action types available in Kizen Agentic Workflows.
Overview
Agentic Workflow control actions manage the execution state of Agentic Workflows, both the current Agentic Workflow and others running elsewhere in the system. Use them to orchestrate multi-Agentic Workflows, handle branching terminal states, loop within a single Agentic Workflow, and keep variable values current as execution progresses.
Note: For error handling, see Agentic Workflow Error Handling.
Start Agentic Workflow
The Start Agentic Workflows action initiates one or more Agentic Workflows from within the current execution. Use Find Agentic Workflows to select the target Agentic Workflow(s).
Choose Record Source: Select one of four options to determine which Record the target Agentic Workflow runs against.
This Record: starts the Agentic Workflow on the current context Record
Related Object: starts the Agentic Workflow on a related Record; select the relationship to traverse using the Choose Related Object dropdown
Record from Agentic Workflow Variable: starts the Agentic Workflow on a Record identified by an Agentic Workflow variable; select a compatible variable from the Agentic Workflow Variable dropdown
None (Global Agentic Workflow): starts a global Agentic Workflow with no associated Record
Resume Paused Agentic Workflows: Available when This Record or Related Object is selected. When enabled, an existing paused execution on the target Record is resumed rather than a new execution being created. When disabled, a new execution is always initiated.
Modify Agentic Workflow
Note: Global Agentic Workflows cannot be targeted by Modify Agentic Workflows.
The Modify Agentic Workflows action changes the execution state of one or more Agentic Workflows running on a related or variable-identified Record. When configuring the step, choose between two operations: Pause or Cancel.
Pause Agentic Workflow
The Pause Agentic Workflow action suspends a running Agentic Workflow. The scope options allow pausing the current Agentic Workflow or another Agentic Workflow running on a related Record or a Record identified from a variable.
Cancel Agentic Workflow
The Cancel Agentic Workflow action cancels a running or paused Agentic Workflow. The scope options allow cancelling the current Agentic Workflow or another Agentic Workflow running on a related Record or a Record identified from a variable. Canceled executions cannot be resumed; if the Agentic Workflow needs to run again on the same Record, a new execution must be initiated.
Go To Agentic Workflow Step
The Go To Agentic Workflow Step action redirects execution to a different step within the current Agentic Workflow.
Steps are grouped by type in the dropdown (for example, triggers appear under a Triggers group header) and are listed in roughly left-to-right order as they appear in the Agentic Workflow builder. The target can be any step type: a trigger, a condition, or another action.
There is a structural constraint to be aware of: a Go To Agentic Workflow Step action cannot have steps placed linearly after it in the same execution path. If steps exist after a Go To Agentic Workflow Step, the builder requires that those subsequent steps either be removed or that the Go To Agentic Workflow Step itself be placed inside a parallel branch. This action is primarily useful for creating loop-like patterns within a single Agentic Workflow.
Note: This action does not include error handling configuration.
Update Variable
The Update Variable action updates the value of an existing variable during execution.
Variable selection: Use the Choose Variable dropdown to select the variable to update. Only variables already defined on the Agentic Workflow are available. If no variables have been defined, the dropdown displays No Options.
Set Variable Source(s): The Source and Fallback Order section is where value sources are configured. Use + ADD VARIABLE SOURCE to add one or more sources. At the point this action runs, available sources are limited to fields on the context Record or other variables. Trigger-based sources are no longer available because the trigger has already been evaluated when the Agentic Workflow started.
Static Value Fallback: The Static Value Fallback section contains a Static (Default) entry with an Enable Static Fallback Value toggle. When enabled, the static value is used if all configured sources resolve to blank.
Error handling: This step includes a Consider empty value an error (Required) toggle.
When enabled, the step treats a blank resolved value as a failure and triggers the configured error handling behavior rather than writing a blank value to the variable.
The step also includes the standard Error Handling configuration. See Agentic Workflow Error Handling.
Stop Execution
The Stop Execution action terminates the current execution and sets it to a specified terminal state.
Use the Action Options dropdown to select one of the following:
Stop and mark as Failed
Stop and mark as Successfully Completed
Stop and mark as Cancelled
Pause and Error
Pause
A Send Notification toggle is available alongside the action selection. When enabled, a notification is sent when the stop action executes.
This action is most useful inside branches where one path should reach a defined terminal state without continuing. For example, if a required condition is not met early in a flow, a Stop Execution step on the no path can mark the execution as failed immediately, without leaving that branch empty or requiring additional steps to reach a natural end.
Note: This action does not include error handling configuration.
Code Step
Code steps allow custom logic to be executed within an Agentic Workflow using a sandboxed runtime environment. For full documentation, see Agentic Workflow Code Steps.
Key Use Cases
Agentic Workflow control actions are applicable across any Workflow that requires coordination between multiple Agentic Workflows, conditional termination, or dynamic variable management. The following examples illustrate common patterns in three industries where execution control is a core operational requirement.
Industry examples
Insurance operations often span multiple Agentic Workflows running across related records, including policy records, claim records, and Contact Records, that must be coordinated as a case progresses.
Examples include:
Starting a claims adjudication Agentic Workflow on a related claim record when a policy Agentic Workflow detects a new claim submission
Pausing a renewal outreach Agentic Workflow when a policyholder record enters a disputed status, and resuming it when the dispute is resolved
Using Stop Execution to mark a compliance review Agentic Workflow as failed when a required field is missing at a critical checkpoint, rather than allowing it to continue in an incomplete state
Using Update Variable mid-execution to capture the current adjuster assignment before routing to a branch that may reassign it
How Agentic Workflow control actions help:
Coordinate work across policy, claims, and Contact Records without building a single monolithic Agentic Workflow
Enforce process gates by terminating executions that cannot proceed due to missing or invalid data
Preserve execution state across pause-and-resume cycles, supporting workflows with human-in-the-loop review steps
Keep variable values accurate throughout long-running executions that span multiple decision points
Healthcare workflows frequently involve parallel processes running across patient, provider, and authorization Records that must be started, paused, or stopped based on clinical events.
Examples include:
Starting a prior authorization follow-up Agentic Workflow on a related authorization Record when a patient intake Agentic Workflow reaches a specific stage
Canceling all pending outreach Agentic Workflows on a patient Record when the patient is marked as discharged or transferred
Using Go To Agentic Workflow Step to loop a document collection Agentic Workflow back to a waiting state until all required documents are received
Using Stop Execution to mark an onboarding Agentic Workflow as successfully completed once all enrollment steps are confirmed, preventing downstream steps from running unnecessarily
How Agentic Workflow control actions help:
Launch downstream Agentic Workflows on related Records at precisely the right point in the patient workflow without manual triggering
Cancel irrelevant in-flight Agentic Workflows when a patient's status changes, preventing stale processes from continuing
Model waiting and retry patterns within a single Agentic Workflow using loop logic rather than building separate Agentic Workflows for each retry state
Enforce clean terminal states on completed workflows so execution history accurately reflects outcomes
Financial services Workflows, including loan origination, onboarding, and compliance reviews, often involve sequential and parallel Agentic Workflows across account, application, and Contact Records that must be tightly coordinated.
Examples include:
Starting a compliance review Agentic Workflow on a related account Record when a loan application Agentic Workflow reaches the underwriting stage
Using Stop Execution to mark a loan application Agentic Workflow as canceled when an applicant withdraws, rather than leaving the execution in an indeterminate state
Pausing a renewal Agentic Workflow when a client Record enters a legal hold status, and resuming it once the hold is lifted
Using Update Variable to capture an intermediate calculation result, such as a debt-to-income ratio, before routing to a branch that applies different logic based on that value
How Agentic Workflow control actions help:
Orchestrate multi-Agentic Workflow Workflows across application, account, and Contact Records without coupling all logic into a single Agentic Workflow
Enforce regulatory and process gates by terminating or pausing executions when required conditions are not met
Maintain accurate execution history by explicitly setting terminal states rather than allowing executions to end ambiguously
Pass computed values forward through long-running Workflows using variable updates, reducing redundant recalculation across steps
What's Next?
Continue to Field Actions to learn how to update and clear field values on the context Record and perform arithmetic operations on numeric fields and variables or check out any of the topics below:
Last updated
Was this helpful?