Environments
- Synopsis
- Full Details
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
- Open the Environments screen and select New Environment.
- Give it a Name and an Environment Type, and select Create Environment.
- Check its page until its services are registered and report Healthy.
The full steps are in Manage environments.
- 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.
- 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.
Task walkthrough: Manage environments. This page is the full configuration and troubleshooting reference.
An environment is a target — such as test or production — that workflows and service requests are deployed to.
Roles decide who can work with environments, through the global Environments permissions. The Environments screen needs Environments View; creating, changing and deleting an environment need Environments Create, Environments Edit and Environments Delete, and the same permissions cover the service addresses registered for it. Reading environments is not checked, so the environment selector lists them for everyone. See Environments and saved searches.
Model
| Field | Notes |
|---|---|
| Name | Unique per tenant. 1–100 characters, and unlike most objects it must read as an identifier: start with a letter or digit, then letters, digits, _ or - only. See Object naming. |
| Description | Optional. Up to 500 characters. |
| Environment Type | DEV, TEST, STAGING or PRODUCTION in the form, shown in the list's Type column as Dev, Test, Staging and Production. The New Environment form starts at DEV. |
| Status | Active, Inactive or Degraded. A new environment starts Active. Once services are registered to it, the status follows their health — see below. |
| Metadata | Free-form key/value used by provisioning. It is not shown on the Environments screens. |
| Last Heartbeat | Nothing reports a heartbeat in the current build, so it stays empty. Use the services' health instead. |
Registered services
Each environment has one or more services:
| Field | Notes |
|---|---|
| Service Type | runtime-service or notification-service, shown as is. |
| Health | Healthy, Unhealthy or Unknown. A newly registered service starts Unknown. |
| Base URL | The service's endpoint. The service's version is recorded too, but the table does not show it. |
| Last Check | When Continuum last checked the service's health. |
Continuum checks each registered service's health in the background and sets the environment's status from the result:
| The environment's services | Status |
|---|---|
| All healthy | Active |
| Some unhealthy | Degraded |
| All unhealthy | Inactive |
An environment with no registered services keeps the status it has. So does one whose services are
a mix of healthy and Unknown with none unhealthy. The Services column on the Environments
list shows how many of an environment's services are healthy out of how many are registered (for
example 1/2), and an environment's page lists each service with its health. Until a service
registers itself with the environment, that list reads No services registered yet — services appear here once they register themselves with this environment.
The environment selector lists only Active environments. A Degraded or Inactive environment drops out of it until its services are healthy again.
An environment is a boundary for what you can reach
A run belongs to exactly one environment, and the platform enforces that when you address one of its jobs directly. A job instance identifier from another environment reports not found — for reading the job, for every action on it (hold, release, cancel, restart, force start, skip, kill, mark fixed, under review, mark finished OK, mark failed, edit), for its output files, and for its history. Reporting not-found rather than "forbidden" is deliberate: it doesn't confirm that the identifier exists somewhere else.
Earlier builds resolved a job-instance identifier without checking which environment it belonged to, so a job in one environment could be read and acted on through another. That's closed.
The same now holds for a whole workflow instance. A workflow-instance identifier from another environment reports not-found for reading it, for hold, release, start, cancel and close, and for its dependency graph and job history — where previously only delete and adding a job to it were checked. As with a job, the answer is not-found rather than forbidden, so it doesn't confirm the identifier exists elsewhere.
One consequence worth knowing: a job whose workflow instance has been deleted now reports not-found too, where its history previously came back empty. There is no environment to place such a job in, and serving a job whose run no longer exists is the worse answer.
How an environment is created
Creating an environment kicks off asynchronous provisioning (a background process that stands up the per-environment runtime service). Provisioning runs fire-and-forget: a provisioning failure is logged but does not fail the create request. So a newly created environment can exist before its runtime is fully ready.
- The Environments screen isn't in the main navigation — it's reachable by direct link.
- A new environment that "isn't working yet" may still be provisioning — check whether its services are registered and what health they report (Unknown/Unhealthy).
- Degraded/Unhealthy indicate the environment's services aren't fully healthy — a deployment target issue, not necessarily a workflow problem.
- Provisioning runs only when the environment is created. There is no way to run it again for an existing environment.
Deleting environments
On the Environments list, select one or more environments and select Delete. The dialog names what it is about to delete and asks you to confirm. Deleting an environment also removes the service addresses registered for it, and releases the resource units its jobs still hold, so they are free for your other environments again.
When some of them cannot be deleted, the dialog says which. The others are deleted, and the dialog stays open with a message that names each environment that was not deleted and the reason. Environments that share a reason share one sentence — Could not delete "TEST-EAST", "TEST-WEST": … — rather than repeating it for each. Only those environments stay selected, so you can deal with them and try again. Earlier builds closed the dialog and cleared the selection as though every delete had worked.
A delete acts only on the environments the list shows. Changing the type or status filter clears the selection, so an environment the filter hides is never deleted.
Troubleshooting
| Symptom | Likely cause | Resolution |
|---|---|---|
| The delete dialog stays open with Could not delete "…" | The platform refused the delete for each environment named; the reason follows the names | Act on the reason, then select Delete again for the environments still selected (Administrator). |
| New environment not running workflows | Provisioning hasn't finished or failed (fire-and-forget) | Check the environment's registered services and their health. Provisioning can't be re-run, so if no healthy runtime service appears, contact support before deleting and re-creating the environment (Administrator). |
| Service shows Unhealthy/Unknown | The registered service isn't reporting healthy | Check the service's endpoint (Administrator). |
| An environment is missing from the environment selector | The selector lists only Active environments, and this one is Degraded or Inactive because some or all of its services are unhealthy | Check its services' health on the Environments screen (Administrator). |
| A job link or identifier reports "not found", but the job plainly exists | The link is for a job in a different environment, or its workflow instance was deleted | Switch to the environment the run belongs to and open the job there (Operator). |
| An action on a workflow instance reports "not found", but the run plainly exists | The run belongs to a different environment than the one you're working in | Switch to that environment and act on the run there (Operator). |
Contact support when
- Provisioning silently failed (the environment exists but its runtime service never registers, or never reports healthy).
Include the environment id/name, type, status, and the registered services' health.