---
schema_version: "1"
id: 122bc3913f592fc3d452f4de9c1117a419474fff80ed023c6167c071026cb2ec
title: How Workflows Lock to a Blueprint Version 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_workflows_lock_to_version.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.automate_afsc_workflows_lock_to_version.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 7f58e47b4b185acff92eae9bb5bba8234fed5ac818ebc01ad98c918ab71de7d6
description: When a workflow starts, it pins itself to the blueprint version that was current at the time. Learn how version locking affects running workflows when updating a blueprint in Agentforce Operations.
products:
  - Cross Cloud
release: "264"
---
# How Workflows Lock to a Blueprint Version in Agentforce Operations

When a workflow starts, it pins itself to the blueprint version that was current at the time. Learn how version locking affects running workflows when updating a blueprint in Agentforce Operations.

### 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="d28732e35">License Required</th>
        </tr>
      </thead>
      <tbody>
        <tr class="">
          <td data-label="License Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d28732e35 ">
            <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>

## Overview

A running workflow is pinned to the blueprint version that it started with. When you publish a new version of a blueprint, the new version only affects workflows created after the new version is published. Active workflows continue to follow the logic of the version they started under.

Version locking protects in-flight work. If you update a blueprint mid-process, you don't disrupt workflows that are already running.

## How Version Locking Works

Running workflows

Continue using the blueprint version that was current when the workflow started, even if you publish a newer version later.

New workflows

Use the latest published version of the blueprint.

Linked workflows

When a parent workflow creates a child workflow, the child workflow locks to the version of the child blueprint that was current at that point. Later updates to the child blueprint don't affect the child workflow.