Deploying sends a tested release to an endpoint. Once the portal confirms the deployment, the endpoint responds to every request with the new release.
- Deploying
- Production endpoints
- When an approval is required
- Going back to an earlier release
- When a deployment fails
Deploying
- On the release page, select "Deploy release" in the top-right corner.
- Under "Where to deploy", choose the endpoint. Each endpoint lists its region and the release currently running under "Now deployed".
- Select "Deploy".
The portal confirms the deployment with "Deployed!". You can see it on the release's "Deployments" tab and in the deployment log.
Production endpoints
An endpoint marked as "Production endpoint" on its settings page has a red "PRODUCTION" badge in the list. When you choose it, the dialog warns that you are deploying to a production endpoint. Deploy the same release to a staging endpoint first and test it there, then deploy it to production.
When an approval is required
An endpoint can require an approval sequence. Until this release is approved for the endpoint, its entry in the list says "Approval required". While approval is pending, the dialog shows "First you need to run the approval sequence." in place of the "Deploy" button.
- Select "Run approval sequence". The approvers receive an email with a link to the approval page, and the release's "Approval process" tab shows the progress.
- After every step is approved, open the deploy dialog again. The endpoint is ready for this release, and "Deploy" is available again.
Going back to an earlier release
Open the earlier release from the release list and deploy it to the same endpoint. The endpoint switches to that release at once, and the deployment log records the change like any other deployment.
When a deployment fails
| Message | Why |
|---|---|
| "This decision flow cannot be deployed to this endpoint!" | The endpoint accepts only certain decision flows, and this release comes from a different one. The endpoint may also require an approval that this release has not yet received. |
| "You do not have enough rights to perform this action." | Your role does not include the right to deploy. Ask an administrator to add that right to your role. See User role. |
| "Something went wrong..." with a reference | The endpoint could not accept the release. Contact support and provide the reference. |
| "First add an endpoint" | No endpoint is available for deployment. Create one first. See API Endpoint. |
Related Documentation: