---
title: "Routing & Conditions"
description: "How to branch a workflow: the Routing panel, branch conditions built with the rule builder, custom logic, and how runs choose a path."
slug: "routing-and-conditions"
audience: "all"
generated_at: "2026-11-17T19:03:12.376Z"
screenshots:
  - "/docs/screenshots/routing-and-conditions/routing-panel.png"
---

The **Routing** panel controls where a workflow goes after a step finishes. Every step in FormAssembly can send each run down exactly one outgoing path, called a branch, and the **Routing** panel is where you add, name, order and remove those branches. Routing is not a step type: it is a setting on an existing step, so you will not find it in the **Add step** menu.

To add and edit steps, see Building Workflows.

## How do I open the Routing panel?

1. Open your workflow and click the **Focus** tab.
2. Find the step whose outgoing paths you want to set.
3. Click the **Routing** action in that step's header.
4. The properties panel opens with the **Routing** heading and lists the step's branches in evaluation order.

Clicking **Routing** again while the panel is open on that step closes the panel. A step that has no outgoing path yet, such as the last step in the workflow, does not show the **Routing** action.

![The Routing panel open beside a step in the builder](/docs/screenshots/routing-and-conditions/routing-panel.png)

## Branch types

A step shows two kinds of branch, and the **Routing** panel makes the difference clear.

- **Built-in outcome branches** come from the step type itself: a connector, email or document generation step has success and failure, a checkout connector also has cancel, an approval step has approved and denied, an e-signature step has signed and declined. Their logic is fixed and read-only. You choose where each outcome goes by building that branch's column of steps, but you cannot add, remove or reorder them.
- **Custom branches** are the ones you add yourself on a form (**Collect**) step, with a condition that reads the response data. You name them, order them and remove them.
- **The Default branch** appears automatically as soon as a step has one custom branch. It carries no conditions, takes no custom name, always sits last, and its summary reads "Handles every other response". FormAssembly keeps it so that every run has somewhere to go.

An assignment step's paths are described in Documents, Signatures & Approvals.

## How do I add a branch?

1. Open the **Routing** panel on the step.
2. Click **Add branch**.
3. Type a name for the branch, such as "New students" or "Refund over $500". A name is optional, and an unnamed branch shows its condition summary instead.
4. In the first condition row, pick a field, then an operator, then a value.
5. Click **Add condition** to add more rows, and set **Match All**, **Any** or **Custom** below the rows.
6. Build the branch's column of steps in Focus view.

Adding the first custom branch also creates the **Default** branch. If the step already led to a linear path, that existing path becomes the Default's column rather than being duplicated or orphaned.

Each new custom branch is created with its own blank **Respond** step named "Thank you", so the branch ends on its own page instead of running into the Default's column. Because that step starts with no message, FormAssembly blocks publishing until you write what that path tells the respondent.

FormAssembly saves your edits to a branch as you make them, including rows you have not finished.

## What can a branch condition read?

A branch condition can read the fields and variables of its own step and of every step before it. A field that was not part of the response, because it was hidden or its step never ran, makes every rule false except **is empty**, which is true. A field left blank counts as empty, so **is not** and **is not one of** are true for it.

Branch conditions use the same rule builder as form conditions, with the same operators, including **is one of**, **is not one of** and **is between**; there is no pattern-matching operator. **is between** takes a From and a To value, and on a choice field **is one of** picks from the field's own options. For the full operator list and how each value control behaves, see Conditions & Validation.

Each condition row carries a letter (A, B, C…) that names its position in the list. Condition rows cannot be reordered; only whole branches reorder. Adding or removing a condition re-letters the list.

A custom branch must have at least one condition. The match selector (**All**, **Any** or **Custom**) appears once a branch has more than one condition, and stays visible while **Custom** is selected.

When a condition compares against another workflow value, the **Routing** panel shows that reference read-only so you can see what the rule compares against. Changing the field or the operator clears it.

## Custom logic expressions

Choose **Custom** below the condition rows to write how the rows combine, using the row letters with `AND`, `OR`, `NOT` and brackets: for example `A OR (B AND C)`. `NOT` binds tightest, then `AND`, then `OR`. Keywords and letters are not case-sensitive.

Every lettered condition must be used exactly once. If you leave one out, the builder says "Condition B isn't used"; if you name one twice, it says "B is used more than once". It also flags a letter that does not exist ("There is no condition D") and unbalanced brackets. An invalid expression is not saved until it is fixed, and the branch keeps the logic it had. An expression the builder accepts shows **Valid** beneath the input.

Switching from **All** or **Any** into **Custom** fills the expression in for you: `A AND B AND C` from All, `A OR B OR C` from Any. Switching back out of **Custom** replaces the expression with every row joined by one operator, with no confirmation. Click **Undo** to reverse it.

Note that a reopened expression is printed from the saved rule, so spacing and letters may differ from what you typed while the meaning stays the same.

## How does a run choose a path?

FormAssembly evaluates a step's custom branches from top to bottom and takes the first branch whose condition is true. If no branch matches, the run takes the **Default** branch. Branch order is therefore precedence: put the most specific branch first, and reorder branches with the drag handle or the keyboard move controls when the wrong path wins.

Built-in outcome branches work differently: the step's own result (success, failure, cancel, approved, denied, signed, declined) decides which one the run takes, so there is no order to set.

Branches that lead to the same next step share that step's column, so you can route two conditions to one follow-up path without duplicating the steps.

To try your branches before publishing, see Testing & Publishing.

## Branching paths on the canvas

Below a branching step's card, the step shows either a row of pills or a row of branch cards, never both. Built-in outcomes appear as pills named for the outcome, such as Success or Approved. Custom branches appear as branch cards, each showing the branch's name and its rule summary, and the branches on the path you are viewing are highlighted. The Default's card reads "Default" with the summary "Handles every other response".

Click an outcome pill or a branch card to switch **Focus** to that path, which keeps your scroll position; a pill that points to a step on the same path scrolls to that step instead. You can also swipe horizontally on a trackpad to move between paths.

Steps before a branch, and steps where paths rejoin, appear on every path. Clicking the branch count above the branch cards opens the step's **Routing** panel.

## Branches Fai writes that the rows cannot show

Fai can write a branch rule that the condition rows cannot display, such as a rule that tests every entry in a repeated section. That branch shows its rule as read-only text in the **Routing** panel, and its summary states the rule in words, or reads "Conditions this editor can't show" when the branch also holds an unfinished row. You can still rename the branch or remove it.

To start the branch's conditions again, click **Replace conditions**. On a form step the branch restarts from one empty row; on an assignment path it restarts from **Responses received** at least 1. **Replace conditions** acts at once, with no confirmation, and **Undo** reverses it.

## How do I remove a branch?

1. Open the **Routing** panel on the step.
2. Find the custom branch you want to remove.
3. Click its remove control.

Removing a branch immediately removes the steps that only that branch reaches; a step another path still reaches stays. The removal and the step deletions are one change, so one **Undo** reverses the whole thing.

Removing the last custom branch also removes the **Default** branch. The step keeps any built-in outcome branches it has.

A branch's only step cannot be deleted, because the branch would have nowhere to go. The builder refuses with "Cannot remove the only step in a branch. Remove the branch instead." Remove the branch itself instead.

## Runs stopped for looping

FormAssembly stops a run that repeats the same cycle of steps 11 times in a row, and emails the owner unless **Email the owner when a step fails** is off, the run is a test, or FormAssembly already tried to send a failure email for that workflow in the last hour. The email's subject is "Action required: step failure in" followed by the workflow name, and its reason begins "Workflow aborted: an excessive loop was detected" and lists the repeating steps by step ID.

A cycle that passes through a Collect, Approval or E-Signature step waits for a person, so it is never stopped this way. If you receive the loop email, use the step IDs it lists to find the cycle, then change those branch conditions so the cycle can end.

## Tips & Troubleshooting

- **Publish or Test is refused and names a branch condition.** One of the branch's rows is missing its field or its value. Open the **Routing** panel on the named step: each incomplete row shows "Missing field" or "Missing value" under the control that needs filling. The marks clear as soon as you fill the half in, and a later successful **Publish** or **Test** clears them all.
- **Publishing is blocked because a new branch's Respond step has no message.** Every new custom branch is created with a blank **Respond** step named "Thank you". Open that step and write the **Confirmation message** the respondent on that path should see.
- **Every response lands on the Default branch.** The condition above it is not matching. Check that the field you picked belongs to that step or an earlier one, and remember that a field the response never included makes every rule false except **is empty**.
- **The wrong branch wins when two conditions could both be true.** FormAssembly takes the first matching branch in the list. Move the more specific branch above the broader one in the **Routing** panel.
- **A branch's conditions show as read-only text.** Fai or the API wrote a rule the condition rows cannot display. Rename or remove the branch as usual, or click **Replace conditions** to start the conditions again from a single empty row.
- **You cannot find the Add step button while building a branch's column.** Structural controls live in Focus view. Click the **Focus** tab; **Overview** is a read-only map of the whole workflow.