Workflow Status v2

Workflow status controls whether the runtime may start a Workflow in a specific Site Environment. The only states are Enabled and Disabled.

Environment scope

Flowgear stores status for each Site, Environment, and Workflow combination. A Workflow can therefore be enabled in Test and disabled in Production, or the reverse.

When you save a new Workflow for the first time in Console, the Console enables it in the selected Environment. Other Environments keep their own status.

Workflow promotion is separate from its enabled or disabled status.

What disabled means

Disabled status prevents new starts through:

HTTP triggers.
Schedule triggers.
Listener triggers.
MCP triggers.
Published Run Now activation.
Calls to the Workflow as a Sub-Workflow.

External HTTP and MCP paths treat a disabled Workflow as unavailable rather than revealing that it exists.

Automatic triggers and disaster recovery

An enabled published schedule or listener Workflow is managed automatically only by the region currently recognized as the active primary. Signing in explicitly to a secondary region does not start another set of these automatic Workflows. See High Availability and Disaster Recovery for failover and recovery checks.

Designer Debug

You can still run a disabled Workflow from the designer in Debug mode. This lets you test a draft without opening its published interfaces to callers.

Debug does not prove that the published revision is current or that the Workflow is enabled. Before testing an external trigger, save and publish the required revision, select the target Environment, enable the Workflow, and verify its authorization and Connection configuration.

Where to change status

Depending on your current Console view, use one of these controls:

On the Workflow landing page, the Workflow Status section lists every Environment you can access and provides Enable or Disable actions.
In the Workflow designer, the top-right Enabled or Disabled switch changes status for the currently selected Environment.
In Manage releases, each Environment row has its own Workflow Status switch when you have access to that Environment.
On the MCP screen, the selected Environment's eligible MCP Workflows have an Environment-specific status control.

Status changes are permission-controlled and recorded in the audit trail. Controls for Environments you cannot administer can be hidden or unavailable.

Status is not the same as publish

Use these terms separately:

Save records the changed source as a revision. The current Console save journey also publishes that revision to the Test Environment.
Publish or promote determines which compiled revision is deployed to an Environment beyond that initial Test publish.
Enable allows the deployed revision to accept new runtime starts in that Environment.
Run or Debug in the designer tests a design interactively and does not replace the other lifecycle controls.