Jump

Category: Integrations

Overview

The Jump node hops the flow to a named target node anywhere in the same recipe. Use it to converge several branches into a shared continuation (a single “thank you” tail), or to retry from an earlier step without duplicating the wiring. A per-node iteration counter caps runaway loops; once the cap is exceeded, the fallback port fires instead of the target.

When to use

Multiple branches that all end at the same Final Message — Jump them all to that node.
Retry-from-earlier-step loops with a built-in cap (e.g. validation failed three times → fallback to a transfer).
Linear-looking flows where you want one canonical exit path.

Ports

Port	Direction	Description
`in`	input	Receives the flow from the previous node.
`jump`	output	Implicit — the runtime advances directly to the configured target node when the iteration cap has not been exceeded.
`fallback`	output	Required. Fires once the per-session iteration counter for this Jump exceeds the configured max.

Configuration

Target node key

The unique key of the node to jump to. Must reference a node that exists in the same recipe — the publish validator (V19) rejects a Jump with a missing or empty target.

Max iterations (default: 3, range 1–50)

How many times this Jump may fire within a single session before the fallback port takes over. The counter is per-session and per-Jump-node, stored inside the session’s variable snapshot, so two separate Jump nodes do not share a counter.

Limits & validation

Publish is blocked if the target node key is missing, points at a node that doesn’t exist, or the fallback port is not wired.
Max iterations must be between 1 and 50; out-of-range values are rejected at publish.
Jump cannot reach nodes in other recipes — use Sub-flow Call for cross-recipe reuse.
Self-loops are allowed (and useful for retry shapes), but the per-Jump cap will eventually fall through to fallback.

Troubleshooting

The recipe falls into the fallback path immediately.

The iteration counter persists across the whole session. If a Condition before the Jump always evaluates the same way, the cap can be exhausted on the very first run-through. Either widen the cap or break the loop via Condition.

Publish blocks with “Jump requires a ‘fallback’ port for max-iteration breach”.

Wire the Jump’s fallback output to a Close, Transfer, or another safe terminal — this is the runtime’s safety net when the loop cap fires.