Agent versioning lifecycle
Key Takeaway
A tested draft must be committed before you can activate it. Committed and active versions are locked, so to change one you create a new version from it and make your changes there.
Agent versioning lets you change an Agentforce agent without disturbing the version that customers or employees already use. Each version moves from an editable draft, to a committed snapshot that can't be changed, to an active version that runs on the agent's channels. To make more changes, you create a new version instead of editing a locked one.
The agent versioning lifecycle
Every new agent, and every new version of an agent, starts as an editable draft. Three actions move a version through its lifecycle: "Save", "Commit Version", and activation. Each one does a different job.
| What it does | Can you still edit the version? | Is the version live? | |
|---|---|---|---|
| Save | Puts your changes into the same draft | Yes | No |
| Commit Version | Saves a snapshot of the version to metadata in your org and locks it | No | No |
| Activation | Makes the agent available on every channel it's connected to, for customers or employees | No | Yes |
Each time you click Save, your changes go into that same draft, so you can keep editing it. A version becomes live only when you activate it.