> For the complete documentation index, see [llms.txt](https://developer.kizen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.kizen.com/docs/concepts/agentic-workflows/agentic-workflow-actions/agentic-workflow-control-actions.md).

# Agentic Workflow Control Actions

{% hint style="success" %}
**Audience:** Administrators, Developers, Solution Architects

**Purpose:** Complete reference for the <code class="expression">space.vars.automation</code> control action types available in <code class="expression">space.vars.Kizen\_company\_name</code> <code class="expression">space.vars.automations</code>.
{% endhint %}

## Overview

<code class="expression">space.vars.automation</code> control actions manage the execution state of <code class="expression">space.vars.automations</code>, both the current <code class="expression">space.vars.automation</code> and others running elsewhere in the system. Use them to orchestrate multi-<code class="expression">space.vars.automation</code>s, handle branching terminal states, loop within a single <code class="expression">space.vars.automation</code>, and keep variable values current as execution progresses.

{% hint style="info" %}
**Note:** For error handling, see [Agentic Workflow Error Handling](/docs/concepts/agentic-workflows/agentic-workflow-actions/agentic-workflow-error-handling.md).
{% endhint %}

***

## Start Agentic Workflow

The Start <code class="expression">space.vars.automations</code> action initiates one or more <code class="expression">space.vars.automations</code> from within the current execution. Use **Find Agentic Workflows** to select the target <code class="expression">space.vars.automation</code>(s).

<div data-with-frame="true"><figure><img src="/files/SoUWrRQfPrd1B63oGXDo" alt="" width="276"><figcaption></figcaption></figure></div>

**Choose Record Source:** Select one of four options to determine which <code class="expression">space.vars.entity</code> the target <code class="expression">space.vars.automation</code> runs against.

* **This Record:** starts the <code class="expression">space.vars.automation</code> on the current context <code class="expression">space.vars.entity</code>
* **Related Object:** starts the <code class="expression">space.vars.automation</code> on a related <code class="expression">space.vars.entity</code>; select the relationship to traverse using the **Choose Related Object** dropdown
* **Record from Agentic Workflow Variable:** starts the <code class="expression">space.vars.automation</code> on a <code class="expression">space.vars.entity</code> identified by an <code class="expression">space.vars.automation</code> variable; select a compatible variable from the **Agentic Workflow Variable** dropdown
* **None (Global Agentic Workflow):** starts a global <code class="expression">space.vars.automation</code> with no associated <code class="expression">space.vars.entity</code>

**Resume Paused Agentic Workflows:** Available when **This Record** or **Related Object** is selected. When enabled, an existing paused execution on the target <code class="expression">space.vars.entity</code> is resumed rather than a new execution being created. When disabled, a new execution is always initiated.

## Modify Agentic Workflow

{% hint style="info" %}
**Note**: Global <code class="expression">space.vars.automations</code> cannot be targeted by Modify <code class="expression">space.vars.automations</code>.
{% endhint %}

The Modify <code class="expression">space.vars.automations</code> action changes the execution state of one or more <code class="expression">space.vars.automations</code> running on a related or variable-identified <code class="expression">space.vars.entity</code>. When configuring the step, choose between two operations: **Pause** or **Cancel**.

<div data-with-frame="true"><figure><img src="/files/rMTLQLSgbZvg2DifeNLw" alt="" width="245"><figcaption></figcaption></figure></div>

## Pause Agentic Workflow

The Pause <code class="expression">space.vars.automation</code> action suspends a running <code class="expression">space.vars.automation</code>. The scope options allow pausing the current <code class="expression">space.vars.automation</code> or another <code class="expression">space.vars.automation</code> running on a related <code class="expression">space.vars.entity</code> or a <code class="expression">space.vars.entity</code> identified from a variable.

<div data-with-frame="true"><figure><img src="/files/Zh4ICpA7fRwuUYixRj9Y" alt="" width="250"><figcaption></figcaption></figure></div>

## Cancel Agentic Workflow

The Cancel <code class="expression">space.vars.automation</code> action cancels a running or paused <code class="expression">space.vars.automation</code>. The scope options allow cancelling the current <code class="expression">space.vars.automation</code> or another <code class="expression">space.vars.automation</code> running on a related <code class="expression">space.vars.entity</code> or a <code class="expression">space.vars.entity</code> identified from a variable. Canceled executions cannot be resumed; if the <code class="expression">space.vars.automation</code> needs to run again on the same <code class="expression">space.vars.entity</code>, a new execution must be initiated.

<div data-with-frame="true"><figure><img src="/files/d9IRybps5E0CCrPFBP8F" alt="" width="248"><figcaption></figcaption></figure></div>

## Go To Agentic Workflow Step

The **Go To Agentic Workflow Step** action redirects execution to a different step within the current <code class="expression">space.vars.automation</code>.&#x20;

<div data-with-frame="true"><figure><img src="/files/ChALKRHJ6QnFk7ZXOZUT" alt="" width="249"><figcaption></figcaption></figure></div>

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 <code class="expression">space.vars.automation</code> 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 <code class="expression">space.vars.automation</code> Step, the builder requires that those subsequent steps either be removed or that the Go To <code class="expression">space.vars.automation</code> Step itself be placed inside a parallel branch. This action is primarily useful for creating loop-like patterns within a single <code class="expression">space.vars.automation</code>.

{% hint style="info" %}
**Note**: This action does not include error handling configuration.
{% endhint %}

## Update Variable

The Update Variable action updates the value of an existing variable during execution.&#x20;

<div data-with-frame="true"><figure><img src="/files/kIXKa2Hizj0Ed0k22K9f" alt="" width="259"><figcaption></figcaption></figure></div>

**Variable selection:** Use the **Choose Variable** dropdown to select the variable to update. Only variables already defined on the <code class="expression">space.vars.automation</code> are available. If no variables have been defined, the dropdown displays **No Options**.

<div data-with-frame="true"><figure><img src="/files/Y8HICrFbZv4fEo6CJRUi" alt="" width="563"><figcaption></figcaption></figure></div>

**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 <code class="expression">space.vars.entity</code> or other variables. Trigger-based sources are no longer available because the trigger has already been evaluated when the <code class="expression">space.vars.automation</code> 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.

<div data-with-frame="true"><figure><img src="/files/k0t2dN2zakCuBSNiZjf9" alt="" width="563"><figcaption></figcaption></figure></div>

**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.

<div data-with-frame="true"><figure><img src="/files/WPCqxlmHSuo49E7xzbNs" alt="" width="563"><figcaption></figcaption></figure></div>

The step also includes the standard **Error Handling** configuration. See [Agentic Workflow Error Handling](/docs/concepts/agentic-workflows/agentic-workflow-actions/agentic-workflow-error-handling.md).

## Stop Execution

The Stop Execution action terminates the current execution and sets it to a specified terminal state.

<div data-with-frame="true"><figure><img src="/files/z5oPKAQRbXQIhN4RH7NB" alt="" width="254"><figcaption></figcaption></figure></div>

&#x20;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.

{% hint style="info" %}
**Note**: This action does not include error handling configuration.
{% endhint %}

## Code Step

Code steps allow custom logic to be executed within an <code class="expression">space.vars.automation</code> using a sandboxed runtime environment. For full documentation, see [Agentic Workflow Code Steps](/docs/concepts/agentic-workflows/automation-code-steps.md).

<div data-with-frame="true"><figure><img src="/files/DunoygT6D1RKClQcsVDW" alt="" width="257"><figcaption></figcaption></figure></div>

***

## Key Use Cases

<code class="expression">space.vars.automation</code> control actions are applicable across any <code class="expression">space.vars.workflow</code> that requires coordination between multiple <code class="expression">space.vars.automations</code>, 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

{% tabs %}
{% tab title="Insurance" %}
Insurance operations often span multiple <code class="expression">space.vars.automations</code> running across related records, including policy records, claim records, and <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entities</code>, that must be coordinated as a case progresses.

Examples include:

* Starting a claims adjudication <code class="expression">space.vars.automation</code> on a related claim record when a policy <code class="expression">space.vars.automation</code> detects a new claim submission
* Pausing a renewal outreach <code class="expression">space.vars.automation</code> when a policyholder record enters a disputed status, and resuming it when the dispute is resolved
* Using Stop Execution to mark a compliance review <code class="expression">space.vars.automation</code> 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 <code class="expression">space.vars.automation</code> control actions help:

* Coordinate work across policy, claims, and <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entities</code> without building a single monolithic <code class="expression">space.vars.automation</code>
* 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
  {% endtab %}

{% tab title="Healthcare" %}
Healthcare workflows frequently involve parallel processes running across patient, provider, and authorization <code class="expression">space.vars.entities</code> that must be started, paused, or stopped based on clinical events.

Examples include:

* Starting a prior authorization follow-up <code class="expression">space.vars.automation</code> on a related authorization <code class="expression">space.vars.entity</code> when a patient intake <code class="expression">space.vars.automation</code> reaches a specific stage
* Canceling all pending outreach <code class="expression">space.vars.automations</code> on a patient <code class="expression">space.vars.entity</code> when the patient is marked as discharged or transferred
* Using Go To <code class="expression">space.vars.automation</code> Step to loop a document collection <code class="expression">space.vars.automation</code> back to a waiting state until all required documents are received
* Using Stop Execution to mark an onboarding <code class="expression">space.vars.automation</code> as successfully completed once all enrollment steps are confirmed, preventing downstream steps from running unnecessarily

How <code class="expression">space.vars.automation</code> control actions help:

* Launch downstream <code class="expression">space.vars.automations</code> on related <code class="expression">space.vars.entities</code> at precisely the right point in the patient workflow without manual triggering
* Cancel irrelevant in-flight <code class="expression">space.vars.automations</code> when a patient's status changes, preventing stale processes from continuing
* Model waiting and retry patterns within a single <code class="expression">space.vars.automation</code> using loop logic rather than building separate <code class="expression">space.vars.automations</code> for each retry state
* Enforce clean terminal states on completed workflows so execution history accurately reflects outcomes
  {% endtab %}

{% tab title="Financial Services" %}
Financial services <code class="expression">space.vars.workflows</code>, including loan origination, onboarding, and compliance reviews, often involve sequential and parallel <code class="expression">space.vars.automations</code> across account, application, and <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entities</code> that must be tightly coordinated.

Examples include:

* Starting a compliance review <code class="expression">space.vars.automation</code> on a related account <code class="expression">space.vars.entity</code> when a loan application <code class="expression">space.vars.automation</code> reaches the underwriting stage
* Using Stop Execution to mark a loan application <code class="expression">space.vars.automation</code> as canceled when an applicant withdraws, rather than leaving the execution in an indeterminate state
* Pausing a renewal <code class="expression">space.vars.automation</code> when a client <code class="expression">space.vars.entity</code> 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 <code class="expression">space.vars.automation</code> control actions help:

* Orchestrate multi-<code class="expression">space.vars.automation</code> <code class="expression">space.vars.workflows</code> across application, account, and <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entities</code> without coupling all logic into a single <code class="expression">space.vars.automation</code>
* 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 <code class="expression">space.vars.workflows</code> using variable updates, reducing redundant recalculation across steps
  {% endtab %}
  {% endtabs %}

***

## What's Next?

Continue to [Field Actions](/docs/concepts/agentic-workflows/agentic-workflow-actions/agentic-workflow-field-actions.md) to learn how to update and clear field values on the context <code class="expression">space.vars.entity</code> and perform arithmetic operations on numeric fields and variables or check out any of the topics below:

<details>

<summary>Related Topics</summary>

* [Field Actions](/docs/concepts/agentic-workflows/agentic-workflow-actions/agentic-workflow-field-actions.md)
* [Related Object Actions](/docs/concepts/agentic-workflows/agentic-workflow-actions/agentic-workflow-related-object-actions.md)
* [Team Actions](/docs/concepts/agentic-workflows/agentic-workflow-actions/agentic-workflow-team-actions.md)
* [Integration Actions](/docs/concepts/agentic-workflows/agentic-workflow-actions/agentic-workflow-integration-actions.md)
* [Messages Actions](/docs/concepts/agentic-workflows/agentic-workflow-actions/agentic-workflow-messages-actions.md)

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://developer.kizen.com/docs/concepts/agentic-workflows/agentic-workflow-actions/agentic-workflow-control-actions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.