Skipping Failed Nodes

Overview

Skip Node lets you manually skip a failed node execution and continue a workflow past the failure — without redeploying, re-triggering, or waiting for the underlying issue to be fixed. In this article, we'll be covering how to mark a node as skippable in the builder and how to skip a failed node from an execution.

Understand how Skip Node works

Skip Node has two parts: a builder-side configuration that marks a node as skippable, and an operator-side action that skips a specific failed execution of that node.

A node must be explicitly marked as skippable before it can be skipped at runtime. When skipping, the workflow resumes from the next node. What the skipped node passes downstream depends on whether an output schema is configured:

• With output schema: The operator is prompted to supply the output data as plain text fields defined in the output schema. The workflow resumes using that data.
• Without output schema: The node is skipped with no output. Any downstream node that references this node's output will receive undefined and may fail.

We recommend configuring an output schema whenever downstream nodes depend on output from a skippable node.

Configure a node as skippable

The Skip checkbox and Output schema field are currently on the Configure tab and will move to a new Error Handling tab in an upcoming release.

1. Open the workflow in the builder.
2. Click the node you want to make skippable.
3. Open the Configure tab in the side panel.
4. Check the Skip checkbox to enable skipping on the node.
5. Optionally, define an Output schema using JSON Schema to describe the output shape a user must supply when skipping.
6. Save the workflow.

Skip a failed node

Skipping a node requires the Workflows > Execution > Edit permission.

1. Open the failed workflow execution from the object's Workflows tab.
2. In the Error log, click the failed error row to open the error detail modal.
3. Review the error details — node name, error code, message, and raw error JSON are shown.
4. Click Skip node.
5. If an output schema is configured, enter the required output data as JSON.
6. Confirm — the workflow resumes from the next node using the supplied output.

Skipping a node with no output schema when downstream nodes depend on its output will cause those nodes to fail. Review the workflow definition before skipping if you are unsure.