Configuration
The Continue node has no configuration. This page covers placement, the signal mechanism, and typical usage patterns.
No configuration required: Like the Break node, the Continue node has zero configurable properties. Drop it into the workflow designer within a Loop body subgraph and connect an incoming wire. When execution reaches it, the
LoopContinueSignal is set and the current iteration is skipped.
Properties
| Property | Type | Required | Default | Description |
|---|---|---|---|---|
| No properties — the Continue node has no configuration. | ||||
Placement Requirements
The Continue node must be placed within the body subgraph of a Loop node:
- It must be reachable from the Loop's body port, through any intermediate nodes.
- It is typically connected as the destination of the "skip this item" branch of an If Condition at the start of the loop body.
- Multiple Continue nodes can exist in the same loop body — whichever is reached first during an iteration will signal the skip.
- Using a Continue node outside a Loop context has no defined effect.
LoopContinueSignal Mechanism
The Continue node communicates with its enclosing Loop node through the execution memory signal system:
- Continue node sets
LoopContinueSignal = truein execution memory. - Continue node fires its
continueoutput port — any connected cleanup nodes execute. - Control returns to the Loop node.
- Loop node detects
LoopContinueSignal = true, clears the flag. - Loop advances
current_indexto the next position. - If more items remain, Loop fires the body port for the next item.
- If no more items remain, Loop fires the done port normally.
Variables set before Continue persist: Any workflow variables written by nodes that ran before the Continue node in the current iteration are NOT rolled back. If you partially update an accumulator variable before a Continue fires, that partial update persists. Design your loop body carefully — either update accumulators after the Continue check, or ensure partial updates are idempotent.
Tip — Place the skip check early: Position the Continue-triggering If Condition as the very first node in the loop body. This ensures that any "guard" checks happen before expensive operations (API calls, database writes) and prevents those operations from running on items that will be skipped anyway. The pattern is: check first, skip early, process only qualifying items.