Skip to main content

Environments

In briefAn environment is a deployment target, such as test or production, that workflows and service requests are deployed to. Each one has its own registered services, and its status follows their health. A run belongs to exactly one environment.

WhereThe Environments screen is not in the main navigation; it is reached by direct link. Its list shows each environment's Type, Status, Services and Last Heartbeat, and an environment's page lists its registered services with their health.

When

  • You are setting up a new deployment target for workflows and service requests.
  • An environment is missing from the environment selector, or a new one is not running workflows.
  • A job or workflow instance link reports "not found" although the run exists.

How

  1. Open the Environments screen and select New Environment.
  2. Give it a Name and an Environment Type, and select Create Environment.
  3. Check its page until its services are registered and report Healthy.

The full steps are in Manage environments.

Notes
  • The Environments screen needs Environments View, and creating, changing or deleting an environment needs Environments Create, Environments Edit or Environments Delete.
  • The environment selector lists only Active environments.
  • Last Heartbeat stays empty in the current build; use the services' health instead.
  • A delete that fails for some of the selected environments keeps the dialog open and names each one with its reason; the rest are deleted.
Watch out
  • Provisioning runs once, when the environment is created, and a failure does not fail the create. If no healthy runtime service appears, contact support before deleting and re-creating it.
  • A job or workflow instance from another environment reports not-found; switch to the environment the run belongs to rather than assuming it was deleted.