Branches
A branch step splits a flow’s execution path based on a condition. Orvanta supports two kinds:
- Branch one: runs whichever branch’s condition is true first; falls back to the default branch if none match.
- Branch all: runs every branch.
Branch one
Section titled “Branch one”A branch one step picks a single subflow to run: it checks each branch’s condition in order and executes the first one that’s true, or the default branch if none of them are. Each branch is itself a flow.
Clicking a branch opens its editor, where you set:
- Summary: a name for the branch, useful once you have more than one — defaults to “Branch 1”, “Branch 2”, and so on.
- Predicate expression: the condition that decides whether this branch runs. It can be a bare
true/falseor a comparison (results.c.command === 'email',flow_input.number >= 2', etc.).
All the branch predicates can also be reviewed together from the parent Run one branch box. They’re checked in the order they’re defined, and the first one to evaluate true wins; if none do, the default branch runs.
Branch all
Section titled “Branch all”A branch all step runs every branch in parallel — again, each branch is its own flow.
Clicking the parent Run all branches box opens the branches editor, where each branch has:
- Summary: a name for the branch.
- Skip failure: when true, a failing branch is skipped rather than failing the whole step.
You can also toggle whether branches run in parallel or sequentially.
Clicking into an individual branch shows the same two settings again:
- Summary: the branch’s name.
- Skip failure: skip this branch on failure instead of propagating the error.
Predicate expression
Section titled “Predicate expression”A predicate expression is the JavaScript condition evaluated to decide whether a branch runs — anything from a plain true/false to a comparison like results.c.command === 'email' or flow_input.number >= 2.