Overview
Health and recent activity for your current scope.
Recent failures
Recent failures in the loaded results.
Runtime
Readiness summary for this process.
Workflows
Workflows and the definitions used for new runs.
Workflow definitions are immutable.
Editing or retiring a workflow creates a draft. Activating it changes future runs. Existing runs keep their original definitions.
| Workflow name | Active definition | Versions | Status | Actions |
|---|
Active
—Workflow
Loading workflow definition…
Workflow map
Steps in the active workflow definition.
StepTerminalFailed
Graph as text
Input parameters
What a caller provides when starting this workflow.
| Parameter | Kind | Referenced as |
|---|
Start sources
Configured ways to start this workflow.
| Source | State | Details |
|---|
Steps
Actions, services, and resources used by this workflow.
| Operation | Service | Action | Resources |
|---|
Active declaration
Published YAML. Draft edits appear in the editor.
Retained definitions
Versions kept for deterministic replay.
| Definition digest | State |
|---|
Recent runs
Recent runs of this workflow.
| Status | Workflow | Workflow ID | Run ID | Started | Duration | Failed step |
|---|
Schedule triggers
Recurring schedules for this workflow.
| Schedule | State | Next run |
|---|
Workflow runs
Live and recently failed executions visible to this scope.
| Status | Workflow | Workflow ID | Run ID | Started | Duration | Failed step |
|---|
Triggers
Configured triggers and their current status.
Active means the trigger is enabled. Inactive means it is disabled or its schedule has not been created. Check provider health separately. Edits take effect after you apply them.
| Trigger | Workflow | State | Kind | Last occurrence | Next occurrence | Actions |
|---|
One-off scheduled starts
Workflows scheduled to start once at a future time.
| Workflow | Due | Workload | State | Run | Actions |
|---|
Editor
Draft, validate, and publish declaration changes.
Restart required
Configuration authoring is not enabled on this host. Enable a managed configuration API or local source authoring to edit declarations.
- 1DraftEdit workflow configuration
- 2ValidateCheck schema and references
- 3PublishCreate immutable revision
- 4ConfirmReview the activation plan
- 5ActivateRoute future starts only
- 6Readiness & auditCheck the activation result
Draft document
Saving a draft does not publish or activate it.
| Workflow | Apply state | Steps | Triggers | Description |
|---|
| Trigger | Apply state | Workflow | Kind or component | Desired state |
|---|
Triggers YAML
All declared trigger kinds; workflows are edited on their own pages.
Components
Components available in your scope. In local mode, this lists services used by loaded workflows. Server credentials and settings are not shown.
Components and services
Approved versions, or services used by local workflows.
| Component or service | Contracts |
|---|
Managed components come from the approved catalog. Local entries show workflow usage and do not grant permissions.
Bindings
Resource and trigger bindings available to your configuration, with their supported capabilities.
| Binding | Capabilities |
|---|
Focused editor
Workflow
Edit one workflow declaration in the draft.
Workflow YAML
Saving updates only this workflow.
Components reference — approved services, actions, and resources
| Service | Actions |
|---|
| Resource | Capabilities |
|---|
Preview
Preview of this workflow. Validate the full draft to check its references.
Graph as text
Releases
Immutable revisions, comparisons, activations, and rollback.
Revision history
Immutable configuration snapshots.
| Revision | Created | Parent |
|---|
Activation history
Activation and rollback records.
| Revision | State | Updated | Actions |
|---|
Activation detail
Status and result of this activation.
Revision
Saved configuration for this revision.
Comparison
Changes between the selected revisions, up to the comparison limit.
| Operation | Path |
|---|
From
To
System
Component readiness for this runtime process.
Runtime health
Required components must be ready before the runtime accepts work; optional components are informational.