- Introduction
- Overview
- What you get with Maestro
- Who should use Maestro
- How Maestro fits into UiPath
- Maestro feature availability
- Getting started
- Process modeling with BPMN
- Process modeling with Case Management
- Designing a persistent case entity schema
- 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)
- Managing live case instances: pause, migrate, and retry
- Maestro case management component dictionary
- Process implementation
- Debugging
- Simulating
- Publishing and upgrading agentic processes
- Common implementation scenarios
- Extracting and validating documents
- Process operations
- Process monitoring
- Process optimization
- Reference information
Maestro user guide
UiPath Maestro™ connects all UiPath components into a single orchestration layer that models, runs, and governs end-to-end processes. Each stage in the lifecycle—Model, Implement, Operate, Monitor, and Optimize—corresponds to a specific purpose and set of platform components.
The following diagram illustrates the five lifecycle stages—Model, Implement, Operate, Monitor, Optimize—and how they align with UiPath products.
Model – Design executable processes
Create automation-ready process models in Studio Web using either BPMN 2.0 or Case Management.
- Purpose: Define workflow logic, triggers, and participants in a visual, executable form.
- Tools: Studio Web (browser-based editor for both BPMN and Case Management), Autopilot for Maestro (prompt-based modeling).
- Outcomes: A validated BPMN model or Case Management plan ready for implementation and execution.
Use BPMN for structured, predictable flows. Use Case Management when work is long-running, exception-heavy, and cannot be fully defined upfront. The two approaches are complementary—a case can invoke a BPMN process as a task. See When to use BPMN Process vs. Case Management and Case management core concepts.
Implement – Add automation, rules, and agents
Enrich your model with automations, AI agents (UiPath or third-party), APIs, and human-in-the-loop steps.
- Purpose: Turn a process design into an executable workflow.
- Tools:
- Maestro for implementation and debugging.
- Orchestrator to manage robots, queues, and triggers.
- Decision Models (DMN) for business rules.
- Outcomes: Fully defined agentic process or Case Management plan deployed as a solution.
Operate – Run and control processes
Manage live instances, supervise tasks, and maintain reliability at scale.
-
Purpose: Ensure processes execute safely and predictably.
-
Tools:
- Maestro Instance Management for pause, resume, retry, and audit of BPMN process instances.
- Case Instance Management for lifecycle controls (Pause, Resume, Cancel, Migrate) and audit of running cases.
- Case App for case workers and managers to view cases, manage tasks, and take case actions.
- Orchestrator for scheduling, triggers, and asset management.
-
Outcomes: Transparent and governed process and case execution.
Monitor – Measure performance
Visualize live process data and detect exceptions.
- Purpose: Track performance, identify failures, and analyze outcomes.
- Tools:
- Insights dashboards for KPIs and telemetry.
- Maestro instance heatmaps and incident tracking.
- Outcomes: Real-time visibility and actionable metrics.
Optimize – Improve continuously
Analyze historical data to identify inefficiencies and test improvements.
- Purpose: Validate conformance and simulate future scenarios.
- Tools: Process Mining and the Process Optimization app.
- Outcomes: Data-driven refinements that shorten cycle times and raise automation ROI.
Together, these connections make Maestro the orchestration hub of the UiPath ecosystem: it leverages the platform's breadth, while the ecosystem empowers Maestro to deliver governed, scalable, and adaptive automation.