Skip to content

Jump – continuing at another command

The command "Jump" continues the action at another command, depending on a condition – or ends the action. This page is for administrators who build actions with branches or repetitions.

Prefer Switch where it fits: an action with a switch can be read from top to bottom, an action with many jumps cannot.

1. At a glance
Purpose Skip commands, repeat commands or end the action, depending on a condition
Typical use "If the record is already approved, end here", retrying a step, leaving a loop early
Where in the editor Toolbar menu "Flow" → "Jump"
Needs a user interface No
Needs a current record No
Related Switch, Actions – errors and how an action ends

2. Settings

The settings are on the tab "Settings". Like every command, the command also has "Display Name", "Description" and "Execution Condition" on the tab "General" (see Actions).

Setting Meaning Default / Required
"Jump condition" Logical expression, evaluated against the current record Required – without it the command is skipped
"Jump if true" Where to continue if the condition is true Empty: continue with the next command
"Jump if false" Where to continue if the condition is false Empty: continue with the next command

Both targets offer "(End Action execution)" and every command of the same list – before or after this one – including the commands inside the cases of a Switch in that list, shown as "Switch / Case / Command". A jump in the pre commands only offers pre commands, a jump in the post commands only post commands.

For an unconditional jump, use a condition that is always true.

3. Behaviour

  1. The condition is evaluated. The target of the matching branch is taken.
  2. Empty target: the action continues with the next command.
  3. "(End Action execution)": the action ends here, without an error. Post commands do not run.
  4. A command: the action continues at that command. It may lie before the jump (the commands in between run again) or after it (the commands in between are skipped). A target inside a switch case runs the rest of that case and then continues after the switch.
  5. A jump inside a loop or a switch case may also go to a command of the surrounding list. The loop or case is left; the remaining passes of the loop do not run.
  6. If the target no longer exists (for example because the command was removed), a warning is written to the log and the action continues with the next command.

4. Examples

End early. First command of "Approve request": Jump with the condition "Status = Approved", "Jump if true" = "(End Action execution)", "Jump if false" empty. An already approved request is left alone. (A guard like this fits even better into the "Execution Condition" of the action, which can also tell the user why.)

Retry up to three times.

  1. Update Variable: "Attempt" = 0
  2. Wait "Pause before retry": 10 seconds, "Execution Condition" "Attempt > 0"
  3. Update Variable: "Attempt" = "Attempt + 1"
  4. HTTP Request, response code into the variable "Status code"
  5. Jump: "Jump condition" "Status code ≠ 200 and Attempt < 3", "Jump if true" = "Pause before retry"

The request is sent at most three times, with 10 seconds between the attempts.

5. Limitations

  • When commands are moved or removed, check the jump targets – they are not adjusted.
  • A jump cannot go into a loop, and the editor does not offer targets inside a loop for a jump that is inside that loop.
  • Jumps backwards can build endless loops. There is no limit on the number of jumps; make sure the condition becomes false.