Workflow Designer Top Bar v2

The designer top bar controls Workflow identity, revision save, Environment and Cluster context, Debug execution, and Environment-specific status.

Workflow identity

Control	Behavior
Back	Returns to the Workflow landing page. Unsaved-change handling can ask you to save or discard before navigation.
Folder	Opens the current Workflow folder in a new tab. A new Workflow uses the folder selected in the explorer, or the Workflow root.
Workflow name	Click the name or edit icon to rename the current design. The name is required.
Suggest another name	Generates another name while the rename editor is open.
Apply or `Enter`	Applies the name to the in-memory design.
Cancel or `Escape`	Discards the current rename draft.

A rename is not persisted as a revision until you save.

Save and more actions

Save opens Revision Management and focuses the commit-message input. Save is available only in the first-ranked Test Environment. When Release Management is enabled, designs opened from later Environments are read-only.

The more-actions menu contains:

Download YAML — downloads the current authored YAML when one is available.
Open relationships — opens Environment-aware dependency information in a new tab when the feature is available and the Workflow has a key.
Open audit trail — opens the Workflow's audit history in a new tab when the feature is available and the Workflow has a key.

Saving a changed design records a revision and publishes it to Test. Saving an unchanged design does not create another history row. See Revision Management Pane.

Environment

The Environment selector controls the context used for status, Connections, published revision information, Debug, and related views.

Each Environment option can show its published revision hash, age, author, and description. In the Test Environment it can also indicate that the latest design will run. In a later Environment, the designer shows a warning describing the published revision that will run or that no revision is published.

Changing Environment can trigger unsaved-change handling. When Release Management is enabled, only Test is editable; later Environments show the published design as read-only.

Cluster

The Cluster selector specifies Cloud or a local Cluster for the Workflow. It is disabled for a read-only design. Changing the Cluster updates the current design and can affect which Nodes and Connections are compatible.

The whole Workflow runs on its selected Cluster.

Run and Stop

Run starts the current design in Debug and expands the Logs tab. The current design still needs a save to become the saved revision.

While starting or executing, Run becomes Stop. Stop requests cancellation, the active Node may take some time to observe it.

In a non-Test Environment, Run uses the published Environment revision and the banner identifies it. Preview and Debug behavior are described in Activation Modes and Timeouts.

Enabled and Disabled

The switch at the right shows and toggles the Workflow's status in the selected Environment. It is separate from save, publish, and Debug.

Enabled permits published invocation and Sub-Workflow calls in that Environment. Disabled blocks them. The control waits while a status update is in progress and is unavailable without an Environment key.