Inspect runs and fix errors

Begin with the first failing node. Inspect its input, resolved parameters, output, logs, and error before changing several parts of the graph at once.

A node never ran#

Check that it has a connected path from Start. For If, confirm which output was selected. For Iterate, check whether the array was empty. A Merge expecting input from a branch that never executes cannot complete that join.

An expression is empty#

Check the producer’s actual output and the expression picker’s scope name. The value must exist on this execution path. Exact expressions preserve their type; expressions inside text become strings. See expressions.

A connection needs setup#

Open the named node and select or add its connection. Missing and disabled connections cannot satisfy a required field. Imported workflows need your own connection bindings.

HTTP or email does not work#

Check the selected runtime. Browser HTTP can be blocked by CORS or other browser restrictions, and email delivery requires Desktop. Then check the destination, credentials, and response from the service.

A blockchain node fails#

Verify the chain, Test mode, RPC route, addresses, and wallet access. For writes, inspect chain activity before repeating the operation; a later error does not prove that an earlier transaction was never submitted.

Retry with intent#

Nodes that expose Retry count and On failure let you configure supported failure behavior. Use retries for operations that are safe to repeat. Some external writes intentionally prevent a whole-node retry after dispatch.

Stopping a run cancels pending work where the runtime supports cancellation. It cannot undo an action already completed by an external system.

Reproduce the issue with the smallest graph that still fails, then add the remaining steps back after the cause is clear.