Skip to main content

Manage environments

An environment is a target (such as test or production) that workflows and service requests are deployed to. Each environment has its own runtime and its own deployed content, so you can move automation from test to production deliberately.

What this solves

Without separate targets for test and production, there's no safe place to try a change. Automation goes straight to production, or test work accidentally runs against live systems.

Create an environment​

To create an environment, complete the following steps:

  1. Go to Environments and add an environment.
  2. Enter a name, choose its type (Dev, Test, Staging, or Production), and add a description.
  3. Save.

Creating an environment starts its provisioning in the background. A new environment may take a short time before its runtime is fully ready. Check its registered services and their health. Provisioning runs only at create and can't be re-run for an existing environment.

What an environment shows​

  • Its type and status (active, inactive, or degraded). The status follows its services' health: all healthy is active, some unhealthy is degraded, all unhealthy is inactive.
  • Its registered services and their health (healthy, unhealthy, or unknown).

The environment selector lists only active environments, so a degraded or inactive one is missing from it until its services are healthy again. No permission covers environments, so roles don't control who can create, change or delete one.

Good to know
  • The Environments screen is reached by direct link (it isn't in the main navigation).
  • If a brand-new environment isn't running workflows yet, it may still be provisioning. Confirm service health before treating it as a fault.
  • A provisioning failure is logged, not surfaced as an error on the create request. If an environment's service health doesn't turn healthy after a reasonable wait, check service health directly rather than expecting a failure notification.
  • Workflows and service requests run in an environment only once they're deployed there. See Version and deploy a workflow.

Related topics