Workflow Will Not Run v2

Determine whether the failure occurs before activation, due to Cluster choice, at a trigger or authorization boundary, or inside a Step.

Identify the activation path

Confirm whether you are using designer Debug, HTTP, MCP, Schedule, listener, Run Now, App invocation, or a Sub-Workflow call. Each has different publish, status, authorization, and input requirements.

Check lifecycle state

For a published path, confirm:

The intended revision is published in the hostname's Environment.
The Workflow is enabled in that Environment.
The trigger metadata matches the caller's Method, route, tool, or schedule.
The API Key or delegated user permits the Workflow and Environment.

Designer Debug can run a disabled draft and therefore does not prove these conditions.

Check Cluster choice and capacity

Confirm the Workflow's selected Cluster has a healthy compatible host and available capacity. Every Node and Connection must support that Cluster.

Check inputs and Connections

Validate required Workflow Parameters, request body shape, trigger context, Connection assignment, and Environment-specific Connection values. Test the Connection from its details screen where supported.

Check logs and timeouts

If an instance exists, open its logs and resolve the first failed Step. A caller can time out or disconnect while runtime work is still cancelling. Stop requests are cooperative, so an external call may take time to observe cancellation.

If no instance log exists, focus on hostname routing, publish, status, authorization, schedule/listener reconciliation, and Cluster dispatch before changing Workflow logic.