Publish, deploy, and promote an agent version
Shipping an agent is three distinct actions. Publish freezes the draft into an immutable version. Deploy puts a version into an entry environment. Promote advances a version one hop along the environment chain toward production. Deploy and Promote share one Deploy menu, which lists each environment with the action it accepts.
Keeping them apart matters, because each has its own preconditions and its own failure mode.
Action | What it does |
|---|---|
Publish | Turns the current draft into an immutable version. A released version never changes — you supersede it rather than edit it. |
Deploy | Puts a version into an entry environment, such as Sandbox, which accepts versions directly. It does not require a published version: the menu offers the current draft too, which is how you try a change in Sandbox before you commit to it. An agent deployed before its first publish starts its version history at version 1, so the deployed version is listed on the Versions tab. |
Promote | Advances a version from one environment to the next in the chain. You cannot skip a hop. |
To deploy or promote an Enterprise agent, a user needs the Create deployments or Promote deployments permission. The Individual Contributor role cannot hold either, so create a custom role for users who ship Enterprise agents. Learn more: Create a role and assign permissions.
Publish a version
- Go to the Agents section in the navigation panel.
- Open the agent.
- Review the draft in the version selector. A draft carries the "Draft has unpublished changes" banner, which offers View current release and Delete draft. The banner appears as soon as you click Create draft, before you change anything. Reset draft to current release appears once the draft differs from the current release.
- Click Publish in the top right. If the editor could not save your draft, it shows the reason, and the tooltip of the Publish button repeats it, starting with "Fix the autosave error before publishing." Publish becomes available after the next successful save.
As a result, Creatio AI Studio freezes the draft into a new immutable version and makes it the current release. The version selector lists the full history — the draft you edit, the current release, and the earlier released versions, each stamped with its author and time.
Deploy a version to an entry environment
- Open the agent.
- Click Deploy in the top right.
- Select the entry environment, for example, the row reading "Sandbox — Deploy v2."
The deployment starts on that click. There is no confirmation step, so read the row before you select it: it names both the environment and the version.
As a result, Creatio AI Studio reports "Deploying v2 → Sandbox…" and the environment moves to a Delivery of "In sync" with a Runtime of "Ready" or "Idle (on-demand)."
Promote a version along the chain
- Open the agent and click Deploy.
- Select the target environment, for example, the row reading "Stage — Promote v1." The menu lists only the environments that can act right now, so an environment with nothing to receive is absent.
As a result, Creatio AI Studio reports "Promoting v1 → Stage…," then "v1 is now serving on Stage." Promotion acts at once, with no confirmation step, which matters most on the last hop into Production.
Promote is unavailable when the source environment has no published release to promote. Creatio AI Studio reports "The source environment has no published release to promote." Publish first, deploy into the entry environment, then promote — a version cannot skip a hop in the chain.
Promotion is also blocked while the source target is unhealthy. Wait for it to recover rather than forcing the rollout forward.
If the agent has trigger bindings in the source environment but none in the target, Creatio AI Studio warns you before promoting. No triggers fire for the agent in the target environment until you add bindings there.
Check what is running where
-
Go to the Deployments section under Runtime in the navigation panel.
-
Review the deployment workspace. It holds one row per agent and environment, in the columns Agent, Environment, Delivery, Runtime, Version, and Action. Counters and filters above the table narrow it to what you are looking for.
Signal
Values
Delivery
Whether the deployed state matches the desired state, for example, "In sync."
Runtime
Whether the runtime is serving: "Ready," or "Idle (on-demand)" while nothing is calling the agent.
As a result, you have the workspace-wide answer to what version each environment runs and whether it is healthy. For one agent across every environment at once, open that agent and go to Configure → ⋯ → Deployments.
Operate a running deployment
Open the ⋯ menu on a deployment row for the following actions.
Action | Effect |
|---|---|
Rollback | Reverts the deployment to its previous version. This is what immutable versions buy you. |
Pause, Resume | Suspends and restores serving without tearing down the runtime. Resume appears only on a paused deployment. |
Cancel rollout | Abandons a rollout that is still in progress and leaves the previous version serving. |
Stop | Stops the deployment and tears down its runtime, reclaiming resources. In-flight requests are interrupted. You can deploy again later. |
View agent details | Opens the agent behind the row, to read its configuration and version history. |
While an environment serves an older release than the latest one you published, for example, after a rollback or after you deploy an earlier release, the Skills tab of the agent shows Deployment update required and names each such environment. The notice clears once every active environment serves the latest published release.