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. Open the Environments screen (it is reached by direct link) and select New Environment.
  2. Enter a Name, choose its Environment Type (DEV, TEST, STAGING or PRODUCTION; the form starts at DEV), and optionally add a Description of up to 500 characters.
  3. Select Create Environment.

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.

Delete environments​

To delete environments, complete the following steps:

  1. On the Environments screen, select the environments you want to delete.
  2. Select Delete, then confirm in the dialog.

Deleting an environment also removes the service addresses registered for it, and releases the resource units its jobs still hold, so your other environments can use them. If any of the environments cannot be deleted, the dialog stays open and names each one with the reason, and only those stay selected; the others are deleted. See Deleting environments.

What an environment shows​

  • Its type and status (Active, Inactive or Degraded). A new environment starts Active. Once services are registered, the status follows their health: all healthy is Active, some unhealthy is Degraded, all unhealthy is Inactive. An environment with no services, or whose services are a mix of healthy and unknown with none unhealthy, keeps the status it has.
  • Its registered services and their health (Healthy, Unhealthy or Unknown). A newly registered service starts Unknown. The list's Services column shows how many are healthy out of how many are registered (for example 1/2).

The environment selector lists only active environments, so a degraded or inactive one is missing from it until its services are healthy again. Opening the Environments screen needs Environments View, and creating, changing or deleting an environment needs Environments Create, Environments Edit or Environments Delete. See Environments and saved searches.

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