Environments carry a status in the dashboard

Environments carry a status in the dashboard (for example draft or active) so you can see which stages are fully set up versus still in progress. Labels and badges in Manage Environments are the source of truth alongside wizard completion.

What you see in the UI

On the Application Environments tab, the table Status column shows a badge:

• active: Environment setup and activation have completed enough for normal operations in the product.
• draft: The Environment exists but the flow is not finished (commonly before Activation completes or before required steps succeed).

Exact colors and wording follow the live UI.

How status relates to the Add Environment wizard

When you Create an environment, the Environment is created early in the flow (after the Environment step) and is typically draft until Activation finishes successfully.

Expected outcome after Activation: Status moves to active and you are routed into the Environment (often to Services) ready to add or migrate workloads.

Draft vs Application draft

An Application can also be draft while the Create New Application wizard is incomplete. See Application lifecycle under Applications in the sidebar. That is separate from an individual Environment’s draft / active badge: an active Application can still contain a draft Environment if you abandoned a second Environment mid-wizard.

Operations and expectations

• Prefer finishing Activation before relying on an Environment for production traffic.
• Use draft Environments as a signal to open the Environment (or Complete Environment Setup) and resolve Compute or activation blockers.
• Changing compute or services may interact with status messaging; trust the dashboard and Compute and worker node issues under Troubleshooting in the sidebar if something stalls.

Related

• Create an environment
• Environments
• Application lifecycle