- Introduction
- Getting started
- Building with Maestro BPMN
- Understanding Maestro BPMN modeling
- Opening the modeling canvas
- Modeling your process
- Aligning and connecting BPMN elements
- Autopilot for Maestro (Preview)
- Process Repository
- Implementing a simple BPMN process
- Implementing a complex BPMN process
- Debugging
- Simulating
- Evaluations (Preview)
- Common implementation scenarios
- Building with Maestro Case
- Introduction to Maestro Case
- Maestro BPMN vs. Maestro Case: when to use case management
- The Maestro Case lifecycle: from event trigger to app experience
- Build your first case with Maestro Case
- Build a Maestro Case with a coding agent (preview)
- Defining case keys (system vs. external)
- Establishing task I/O and write-back contracts
- Exit rules and early stage termination
- Modeling primary and secondary stages
- Triggering a case from Data Fabric
- Implementing stage-level personas and permissions
- Setting SLAs and automated escalation rules
- Configuring a rework loop (re-entry)
- Configuring and testing the Case Manager Agent (preview)
- Case Manager input and output contract
- Maestro Case component dictionary
- Building with Maestro Flow
- Maestro Automate
- Integrations
- Operating
- Monitoring
- Optimizing
- Reference information
Preview process behavior in Maestro before production by simulating control flow, inspecting variable changes, and identifying design flaws without executing against live systems.
Simulation in Maestro lets you preview how a process will behave—without executing it in production. You can validate control flow, inspect variable changes, and identify design flaws early, before connecting to robots or external agents.
You can simulate both:
- Control flow: sequences, conditions, and gateways
- Data flow: inputs, outputs, and variable propagation
This makes it easier to understand the end-to-end behavior of your process during design.
When to use simulation
Use simulation to:
- Preview how a process behaves before implementation
- Validate logic early in the design phase
- Explore conditional flows and gateway outcomes
- Test data movement without requiring robots or agents
Simulation is especially useful during iterative design or when working with large, modular processes.
How simulation works
Simulation does not run the actual tasks (such as robot jobs, API calls, or agent actions). Instead, it:
- Evaluates sequence flows.
- Lets you choose which outgoing path to follow at gateways.
- Highlights the simulated path directly on the canvas.
- Displays current variable values in the right panel.
- Lets you pause and resume execution at any step.
You can inspect the simulation trace and data values at each step to confirm expected behavior.
Running a simulation
To simulate your process in Studio Web:
- Select a Maestro process inside your solution.
- Open the context menu for a Start element in the process and choose Simulate.
- Select Start Simulation. The simulation begins immediately from that Start event.
Result
The simulation starts from the selected Start event and the process is visualized on the canvas, with each executed path highlighted. The execution trail shows the status of each step and any detected incidents.
The process will simulate visually—each path will be highlighted based on logic execution. The execution trail shows the status and the corresponding step, as well as the detected incidents.
During the run you can:
-
Switch gateway paths: when reaching a gateway, choose the outgoing branch to follow.
-
Pause execution: Open the context menu for the element and select Add pause. The simulation will stop when it reaches that element. You can also point to the canvas and select the pause icon when it appears to add pause in that particular place.
-
Resume execution: Open the context menu for the paused element and select Remove pause to continue. You can also point to the canvas and select the pause icon when it appears to remove pause in that particular place.
Simulation tips
Table 1.
| Tip | Description |
|---|---|
| Observe gateway logic | You select which branch to follow. This helps verify the modeled alternatives. |
| Review parallel/multi-instance behavior | You can visualize parallel paths or iterations with lists. |
| Test incomplete models | Simulation runs even if tasks are not fully configured, allowing safe iteration. |
Limitations
-
Simulation does not invoke robots, agents, or integrations.
-
Gateway conditions are not auto-evaluated—you must choose the branch.
-
Use Test mode for live execution when you need to validate actual integrations and system connections.