---
schema_version: "1"
id: 38d822b4eefd52939622ee6fe3a1b7a60f256cbd3a3d1ac6102ca4255158c0ed
title: How Conditional Branching Works in Agentforce Operations
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/automate_afsc_blueprints_conditional_branching.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.automate_afsc_blueprints_conditional_branching.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 7c7b6c2c773992e9224b184204c73b964fd3c554426a00902a894204d0598b03
description: Learn how conditions on stages control which path a workflow follows and what happens when conditions are or aren't met.
products:
  - Cross Cloud
release: "264"
---
# How Conditional Branching Works in Agentforce Operations

Learn how conditions on stages control which path a workflow follows and what happens when conditions are or aren't met.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
      <colgroup>
        <col>
      </colgroup>
      <thead class="slds-text-title_caps ">
        <tr class="">
          <th scope="colgroup" class="slds-cell-wrap" colspan="1" style="text-align:left;vertical-align:top;" id="d32884e35">License Required</th>
        </tr>
      </thead>
      <tbody>
        <tr class="">
          <td data-label="License Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d32884e35 ">
            <p>This feature is a workspace that’s external to your Salesforce org and requires
              an Agentforce Operations license. </p>
            <p style="margin-bottom:0;">To purchase an Agentforce Operations license, contact your Salesforce account
              executive.</p>
          </td>

        </tr>
      </tbody>
    </table>

## How Conditional Branching Works

By default, stages in a blueprint run in sequence: Stage 1 completes, then Stage 2 starts. Conditional branching changes that. You add conditions to a stage so it starts only when it meets specific criteria. Stages where conditions aren't met are skipped.

Conditions evaluate field values from earlier stages by using operators such as `equals`, `greater than`, or `is empty`. You can combine multiple conditions with AND or OR logic, and group conditions together to create more complex rules.

## When to Use Conditional Branching

- A process has different approval paths based on dollar amount, risk level, or region.
- Some stages only apply to certain product types, supplier tiers, or request categories.
- You want to skip optional stages when a field is blank or a checkbox is deselected.
- Different teams handle different parts of the same process based on the input data.

## Supported Field Types

You can use all field types and data sources as conditions except Document fields.

## Key Concepts

Mutually exclusive branches

When two stages have conditions that can't both be true at the same time. For example, Contract Value field greater than or equal to 100,000 and Contract Value field less than or equal to 100,000, only one branch runs.

Parallel branches

When two stages have conditions that can both be true, both stages run at the same time. Use overlapping criteria when separate teams work in parallel.

Merging branches

Use the **After specific stages** start condition to bring branches back together. Select all the stages that could be the last stage before the merge point. The merge stage waits for whichever branch actually ran to finish.