maestro
2.2510
true
Maestro Orchestrate user guide
- Introduction
- Getting started
- Process modeling
- Process implementation
- Debugging
- Simulating
- Publishing and upgrading agentic processes
- Common implementation scenarios
- Extracting and validating documents
- Process operations
- Process monitoring
- Reference information
- Maestro Orchestrate and ReFramework FAQ
- Downloads
- Known issues
Maestro Orchestrate and ReFramework FAQ
Guidance on when to use Maestro Orchestrate versus ReFramework: long-running multi-actor flows, queue-based UI tasks, and combining both approaches.
Does Maestro Orchestrate replace ReFramework?
- No. Maestro Orchestrate orchestrates end-to-end processes. The ReFramework still supports running transactional UI performers, especially those that are queue-driven.
When do I use one or the other?
- Use Maestro Orchestrate for long-running, multi-actor flows. Use ReFramework for robust, queue-based UI tasks. Use both when a process needs orchestration plus reliable execution.
How do we use Queues in an Agentic Process?
- Have Maestro Orchestrate start jobs or create queue items, let ReFramework performers process them.
How do we keep REFramework "economies of scale" (log in once, do many)?
- Keep using Queues and Robot Performers for batched UI work. Maestro Orchestrate orchestrates around them.
Should ReFramework ever be used with an Agentic process?
- Yes. Use ReFramework for the RPA performers. Maestro Orchestrate orchestrates the end-to-end flow. Only RPA robots should be queue performers.
Can’t we already do everything with ReFramework?
- You can, but you pay an "orchestration tax": custom chains of queues or state tracking, brittle cross-step retries, weak visibility. Maestro Orchestrate provides native process-level control.
Why isn’t Maestro Orchestrate, or an Agentic Process, a queue "performer" (reading directly from a Queue)?
- Maestro Orchestrate is the orchestrator. Queue performers will remain for RPA robot. An Agentic process maps 1:1 to a unit of work, which is effectively the queue item. This implies that the process is the "queue", not a consumer of it. If you need Maestro Orchestrate to drive off work, modify or replace the dispatcher to invoke Maestro Orchestrate directly (Run Job) instead of creating a queue item.
Read more about UiPath Maestro Orchestrate™ and REFrmework.
- Does Maestro Orchestrate replace ReFramework?
- When do I use one or the other?
- How do we use Queues in an Agentic Process?
- How do we keep REFramework "economies of scale" (log in once, do many)?
- Should ReFramework ever be used with an Agentic process?
- Can’t we already do everything with ReFramework?
- Why isn’t Maestro Orchestrate, or an Agentic Process, a queue "performer" (reading directly from a Queue)?