Understand workflow validation

Errors

Errors are problems that prevent the workflow from running correctly, such as missing triggers or disconnected steps. You cannot publish a workflow that has errors.

Warnings

Warnings are issues that do not prevent execution but might cause unexpected behavior. You cannot publish a workflow that has unresolved warnings.

When validation runs

Automation orchestrator runs validation at the following points:

• Save. When you save a workflow, validation runs automatically. The save always succeeds, even when errors or warnings are present. Automation orchestrator flags the workflow as having unresolved issues and displays the findings so you can address them.
• Publish. When you publish a workflow version, validation runs and blocks publishing if any errors or warnings exist.
• Run. When you run a workflow, validation runs to confirm the definition is executable.
• On demand. You can validate a workflow definition without saving by using the validation API endpoint.

How validation works in the workflow builder and API

Automation orchestrator validates your workflow at two levels:

• Workflow builder validation. The workflow builder checks for structural issues such as orphaned nodes, invalid connections, and unconfigured steps when you verify, publish, or run a workflow, and when you reopen a workflow that was saved with unresolved issues. Results appear in a verification banner above the canvas and as warning badges on affected nodes.
• API validation. The API checks reference integrity, variable resolution, and cross-node dependencies that require the full workflow definition when you save, publish, or run a workflow.

Both levels must pass before you can publish a workflow.