A process version is a snapshot of a Process Builder process at a point in time. Because an active process cannot be edited directly, Salesforce makes you clone an active process to create a new version, edit that, and then activate the new version (which deactivates the old).
Why versioning exists
Without versions, editing an active process would either:
- Break records mid-save if you changed criteria, or
- Force you to deactivate, edit, and reactivate — leaving a window of no automation
Versions sidestep both. You can build and test version 2 while version 1 keeps running.
How the version model works
| Action | Effect |
|---|---|
| Open an active process → click Clone | Choose Version of current process — creates a new editable version |
| Open an inactive version → edit | Allowed because it’s not running |
| Activate a version | Deactivates whichever version was previously active |
| Delete an inactive version | Allowed — removes that version permanently |
| Delete the active version | Not allowed — deactivate first |
Only one version of a given process can be active at a time.
The lifecycle
- Build v1, activate it. Records start running through it.
- Need to change behaviour: open v1, click Clone → Version. v2 is created in Draft.
- Edit v2 in Process Builder. v1 is still running in production unchanged.
- Test v2 in a sandbox or via a User who can preview.
- Click Activate on v2. Salesforce activates v2 and deactivates v1.
- If v2 has bugs, deactivate it and reactivate v1 — instant rollback.
What survives between versions
- All actions you defined
- All scheduled actions already in the queue (queued under v1 keep firing under v1’s logic even after v2 is active, until they complete)
- Audit history at the process level
This last point is important: scheduled actions queued by an older version don’t migrate to the new version’s logic. They fire under the old logic. If you change scheduled-action behaviour, you may need to manually clear the queue or wait for old entries to age out.
The Flow equivalent
Flow uses the same versioning model — every Flow has versions, you clone to a new version, activate one at a time. The mental model from Process Builder transfers directly. Flow’s UI also lets you label versions (“v2 - added VIP path”) which is helpful for tracking.
Common interview catch
Candidates sometimes think versions are just for tracking history. They are also the mechanism for safe iteration on a live automation. Calling that out shows you understand the real reason versioning exists.
What interviewers want
- The definition: a clone-and-replace mechanism for editing active processes
- The constraint: only one active version per process
- Bonus: that queued scheduled actions don’t auto-migrate when you activate a new version
Verified against: Salesforce Help — Process Versions. Last reviewed 2026-05-17 for Spring ‘26 release.