In AI Agent Workflows, an alternative branch is a configured route for a condition result or a value that does not match a Router rule. It is not an automatic exception handler for a failed action. Choose the mechanism that matches the situation you need to handle.
For a step-by-step guide to checking absent or empty values before branching, see Handle Missing Workflow Data.
Configure a Condition’s unmatched route
- Select the Condition node in the workflow editor.
- Configure the condition rows and choose the step each matching condition should run.
- Set the No Condition Matched target to the step that should run when every condition is false.
- Connect the intended follow-up actions to that branch and keep the normal path separate.
- Test a payload that matches a condition, then test one that matches none of them.
Screenshot to add: Condition node No Condition Matched branch target
Router default target
The Router action schema defines Value to check, Matching rules, and Otherwise, run this step. At runtime, the Router trims the checked value and compares it with each non-empty route match using a case-insensitive text comparison. The first matching route is selected. If no route matches, the configured default target is returned.
Important limitation: in the inspected version 0.1.3, the builder source does not contain a dedicated configuration control for the Router’s Matching rules field. Do not assume this route configuration is fully available in the editor UI. Confirm the installed build exposes it before using Router for a production workflow.
Node errors are separate
A condition that evaluates false is still a successful Condition-node execution. A missing branch target means no branch step is selected; neither case is the same as an action failure.
For actual node failures, the global On node failure setting in the plugin’s settings controls whether execution stops or continues running the remaining nodes. The default is to stop. Continuing the remaining nodes does not route the failed node to a dedicated error branch, and it may allow later steps to run without the output they expected. The AI Agent node also has its own error behavior, but that is specific to the agent node and is not a general fallback path.
Verify the intended path
- Run a test in which one configured condition matches and confirm its selected step runs.
- Run a test in which no condition matches and confirm the configured No Condition Matched target is used.
- If using Router, test a matching value and a non-matching value only after confirming the route controls are available in your installed editor.
- For node errors, inspect the node’s result and run log separately, and review the global On node failure setting.
Screenshot to add: Workflow run log comparing a matched branch, unmatched condition, and node error