Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Deployments and approval requirements

Deployment stages let you release workflow versions through separate environments. Set approval requirements for each stage to control when a version becomes available.

Before you start

A stage is a separate release destination, such as testing or production. Before changing approvals, agree who owns each stage and who will review it. Keep Create environment variables and Assign and secure an environment separate from release approvals: the target stage also needs the correct configuration values.

You need permission to configure deployment stages. Required reviewers must have access to the proposed workflow.

Configure stage approvals

Open Deployments and inspect Required Approvals for each stage.

Required Approvals for deployment stages

A zero-approval policy can deploy immediately, so use the approval requirements set by your team.

Submit a version to a stage

Save the candidate change and run the draft.

Candidate draft test

Confirm the intended behavior before creating a deployment request.

Select Create Pull Request and describe the change for the intended stage version.

Deployment pull request description

Check the target environment and version before submitting.

Open Deployments and confirm the new version is Pending.

Pending deployment version

The previous deployed version remains active until the request meets the deployment requirements.

Review the proposed version

Have an authorized reviewer open View PRs for the pending version and select Review.

View PRs and Review controls

The reviewer should read the description before inspecting the candidate.

Run the candidate in the review workspace and inspect its output.

Candidate test in the review workspace

Review the proposed behavior without changing the working draft.

Open Review Pull Request and inspect all Proposed Changes before accepting.

Review Pull Request and Proposed Changes

Include configuration and connection changes, not only the most visible instruction edit.

Verify the deployed version

Return to Deployments and confirm the intended version is Deployed.

Deployed version and stage details

Check Deployed By and the stage so you know which deployment changed.

Open that stage's Deployment URL and inspect a response.

Stage Deployment URL response

A successful check in one stage does not confirm the state of other stages.

Recover a stage after a failed release

Use Redeploy to return a stage to a version previously deployed to that same stage. This is a release action: an eligible redeployment updates the stage directly without creating a new approval request. It requires permission to update the project. Follow your team's incident ownership process before confirming it.

  1. Record the affected stage, its current version, and the failing input. Locate a known good version in the stage's deployment history and review its configuration and previous test results.

  2. Choose Redeploy to [stage] for that historical version. In Redeploy Version, check both the version number and the stage, then choose Redeploy.

  3. Confirm the success message and the stage's current version. Open that stage's Deployment URL in a fresh conversation, submit representative input, and inspect the response. Production redeployment also changes the published workflow version.

  4. Record the incident and redeployment, then repair and test the working draft before the next release. Redeploying a stage is not a restoration of the editor draft, nor does it undo actions that earlier runs already performed in external services.

Redeploy is unavailable for Draft, the version already active in the stage, a version never deployed to that stage, or a stage outside the project's configured stages. A pending request for the same target version and stage blocks redeployment. Have the release owner resolve that request deliberately rather than changing approval requirements to bypass it. If no eligible historical version is available, prepare a corrective version and use the normal release process. Escalate an unexpected error with the project, stage, version, and message through Support and deployment diagnostics.

Important behavior

A pending request leaves the current stage version in place. Stages with no required approvals can deploy immediately.

Check the stage URL when verifying a release. The editor draft may contain changes that have not reached that stage.

Last updated

Was this helpful?