Input & Output
Continue port, signal processing, and the state of the execution context after a skipped iteration.
Output Ports
| Port | When Triggered | Description |
|---|---|---|
continue |
Immediately when the Continue node executes | Fires after setting LoopContinueSignal. Optional cleanup or skip-logging nodes can be connected here. After any connected nodes complete, control returns to the Loop node which advances to the next iteration. |
Execution Memory Written by Continue
| Memory Key | Value | Cleared By |
|---|---|---|
LoopContinueSignal |
true |
Cleared by the Loop node after it detects the signal and advances to the next iteration |
Data Flow — Skipped Iteration
// === Array: 4 items ===
// items = [
// { id: "A", active: true },
// { id: "B", active: false }, // ← this item will be skipped
// { id: "C", active: true },
// { id: "D", active: true }
// ]
// === Iteration 1: item A (active = true) ===
// If Condition: "$var.current_item.active !== true" → false
// Proceeds to processing nodes. ProcessItem executes.
// === Iteration 2: item B (active = false) ===
// If Condition: "$var.current_item.active !== true" → true
// → Continue node fires
// Sets LoopContinueSignal = true
// Fires "continue" port (e.g., LogSkip node runs)
// Loop detects signal → clears signal → advances to item C
// === Iteration 3: item C (active = true) ===
// If Condition: false → proceeds to ProcessItem
// === Iteration 4: item D (active = true) ===
// If Condition: false → proceeds to ProcessItem
// === Done port fires ===
{
"loop_completed_normally": true,
"loop_total_items": 4,
// 3 items were processed, 1 was skipped
// Accumulator variables reflect results of items A, C, D only
}
Difference Between Continue and Not Connecting a Port
You might wonder: if the Continue just skips remaining body nodes, can you achieve the same by simply not connecting any nodes after the If Condition's "skip" branch? The answer is yes — for simple cases, leaving the branch unconnected has the same effect. However, the Continue node provides two important advantages:
- Explicit intent: The Continue node makes it visually clear in the workflow graph that this is a deliberate "skip this iteration" decision, not an accidental unconnected wire.
- Optional skip-path logic: Nodes connected to the Continue's output port can execute cleanup logic (e.g., logging the skipped item, incrementing a skip counter) before the loop advances. An unconnected wire cannot do this.