Jump Flow Node

The Jump Flow Node transfers execution to another flow entry and does not come back. The current flow ends when control is handed off.

What it serves

Almost the same as Run Flow — but instead of calling a sub-flow and returning, this is a one-way transfer. The flow you started in ends here; the target flow takes over.

Common shape: a Condition Node decides which of two endings the flow takes, and each branch jumps to a different terminal flow:

                    ┌─ TRUE  ──► [Jump Flow: SuccessFlow-Start]
[Condition Node] ───┤
                    └─ FALSE ──► [Jump Flow: FailureFlow-Start]

Each Jump Flow lands the request in a different completion flow; neither comes back.

Visual

The node has one dot — IN on the left only. There's no OUT, because execution doesn't continue past it. The body shows a green down-arrow icon (the Jump Flow symbol).

Settings

Click the node to open Jump Flow Node Settings:

Field	Purpose
Flow Name	The entry to jump to, in <Controller>-<StartNode> form. Example: MyFlow-StartNode.
Node Description	Free-text — for other developers. Doesn't affect execution.
Apply	Saves the settings.

Same form as Run Flow — same shape of value.

How dictionary is shared

The target flow runs against the same dictionary instance as the calling flow. Whatever's been built up by the time you Jump goes with you.

(Same rule as Run Flow — only the return-vs-no-return behaviour differs.)

When to use Jump Flow vs Run Flow

Need	Use
Call a sub-flow and continue the current flow afterwards	Run Flow
Hand off to a different flow as the terminal step	Jump Flow

If you find yourself putting a Run Flow at the very end of a flow with nothing after it, use Jump Flow instead — it's the right tool for "this flow ends by going there."

Failure behaviour

Same as Run Flow: if the target flow fails, the whole request fails. There's no error edge.