You are here:
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.
| License Required |
|---|
This feature is a workspace that’s external to your Salesforce org and requires an Agentforce Operations license. To purchase an Agentforce Operations license, contact your Salesforce account executive. |
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.
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.
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.