Troubleshooting

Use the editor's Status panel when a workflow is blocked or shows warnings. Each row explains what is wrong, and rows tied to a node can be clicked to select that node on the canvas.

Missing configuration

Open the affected node and fill in the required fields. Most missing configuration issues are resolved from the node's settings panel.

Common examples:

• Missing credentials, model, prompt, or JSON input on an AI node
• Missing URL on an HTTP request node
• Missing schedule on a cron trigger
• Missing expression, route, code, or transform input on logic and utility nodes

See Configuring Nodes for the editor workflow.

No trigger

Add a trigger node before running the workflow. A trigger defines how the workflow starts.

See Triggers for trigger types and Manual Trigger for test runs.

Circular dependency

Remove any connection that loops back to an earlier node. Workflows run in graph order, so cycles cannot execute.

See Edges for how connections define execution order.

Schedule problems

If a scheduled workflow is blocked, open the cron trigger and confirm that a cadence is selected. Then activate the schedule from the editor header.

See Cron Trigger for schedule setup.

Runtime failures

If the workflow starts but fails during execution, open the Executions panel and select the failed run. Failed nodes show their error output and timing details.

See Running a Workflow for execution inspection.