- Introduction and getting started
- Maestro landing page
- Process modeling
- Process implementation
- Process operations
- Process monitoring
- Process optimization
- Licensing
- Reference information
Maestro user guide
A sequence flow in BPMN shows the order in which flow elements—such as tasks, events, and gateways—are executed in a process. In Maestro, sequence flows represent the control logic that drives agentic behavior, transitions between steps, and branching logic based on conditions or rules.
In UiPath Maestro™, sequence flows are not just visual links—they orchestrate how work moves between agents, robots, and humans. When testing or executing a process, sequence flows guide the runtime engine on which task to activate next and under what conditions.
Sequence flows are used to:
- Connect all executable elements (tasks, gateways, events).
- Control branching after decision points.
- Specify default or fallback paths.
- Attach conditional logic to determine routing at runtime.
A sequence flow in BPMN shows the order in which flow elements—such as tasks, events, and gateways—are executed in a process. In Maestro, sequence flows represent the control logic that drives agentic behavior, transitions between steps, and branching logic based on conditions or rules.
In UiPath Maestro™, sequence flows are not just visual links—they orchestrate how work moves between agents, robots, and humans. When testing or executing a process, sequence flows guide the runtime engine on which task to activate next and under what conditions.
Sequence flows are used to:
- Connect all executable elements (tasks, gateways, events).
- Control branching after decision points.
- Specify default or fallback paths.
- Attach conditional logic to determine routing at runtime.
Maestro supports the following types of sequence flows:
| Type | Description |
|---|---|
| Unconditional | A flow with no conditions—always followed if reached. |
| Conditional | Contains an expression that must evaluate to true for the flow to be taken (typically after a gateway). |
| Default flow | The fallback flow from a gateway if no other conditions are met. Default flows are marked with a slash. |
Conditional sequence flows support simple or complex logic based on:
-
Input variables
-
Rule results (DMN)
-
Runtime values passed through the process
For example, after an exclusive gateway:
- Flow A:
amount > 10000amount > 10000 - Flow B (default): No condition
- Connect every element with sequence flows—floating tasks or gateways break execution.
- Label conditional flows for clarity during testing or handoff.
- Use default flows with exclusive gateways to ensure predictable behavior.
- Modularize complex logic using sub-processes and keep branching shallow when possible.
