September 2026

September 2026 release notes for Maestro in Automation Cloud and Test Cloud.

September 22, 2026

Cartographer now feeds into the Model – Design executable processes stage

Cartographer, Delegate's profile for documenting and redesigning business processes, now sits upstream of the Model – Design executable processes stage of the Maestro lifecycle. Cartographer generates a Process Design Document (PDD) and Specification Design Document (SDD) that inform the BPMN (Business Process Model and Notation) or Case Management model you build in Studio Web.

For details, see How Maestro fits into UiPath. For Cartographer's own capabilities, refer to Cartographer overview.

September 18, 2026

Maestro Automate is now generally available

Maestro Automate ships alongside Maestro Flow, for short-running workflows of AI agents and APIs. It uses the same canvas and the same engine, with a lightweight runtime envelope and a run price sized for work that finishes within minutes or hours. You choose it when you create the project and the platform governs it from the first run. You can convert between Maestro Flow and Maestro Automate: they share the same functional components but have different instance management, runtime, and licensing considerations.

For details, refer to the following pages:

• What is Maestro Automate?
• Choosing between Maestro Orchestrate and Maestro Automate

September 17, 2026

Maestro Flow is now generally available

Maestro Flow is now generally available. It is the third canvas in Maestro Orchestrate, alongside Business Process Model and Notation (BPMN) and Case, and it is built for developers: agents, APIs, robots, documents, data, and human steps composed inline on one canvas, and co-developed with coding agents in the editor you already use.

General availability means Flow processes are supported for production use, on the same Maestro engine as BPMN and Case processes, with the same durable execution and instance control.

Where you build

• Your editor — VS Code and its forks (Cursor, Antigravity, Kiro) through the Maestro extension on the VS Code Marketplace and Open VSX, Studio Web with nothing to install, and Studio Desktop alongside RPA.
• Coding agents — Claude Code, Codex, Cursor, and Copilot author .flow files, configure nodes, and validate end to end through the uip CLI, with the canvas rendering the result so a person can review and correct it.

What you compose

• AI agents — Autonomous agents configured on the canvas, or written in code and added as nodes. Third-party agents connect over Model Context Protocol (MCP) and Agent2Agent (A2A), with context, guardrails for personally identifiable information (PII) and prompt injection, and inline testing.
• Connectors — Enterprise and custom connectors, HTTP requests, webhooks, and triggers and wait-for-event steps driven by external systems.
• Data — Read, create, update, and delete Data Fabric entities as native nodes, without leaving the flow.
• Documents — Extract, summarize, and classify documents inline, with structured data passing straight into your logic.
• Humans in the loop — Quick Forms for approvals and escalations on the canvas, and Action Apps for richer custom interfaces, delivered in Slack, Teams, email, and Action Center.

How you validate and operate

• Evaluations — Agent and flow trajectory and results validated with LLM-as-judge or exact match, with performance tables, detailed tracing, and a guided path from any debug run to an evaluation set. Evaluation runs are free.
• Maestro Orchestrate runtime — Every Flow instance runs on the same Maestro engine as BPMN and Case, with durable execution and no cap on duration or concurrency, so a flow can wait days and resume exactly where it stopped. Live instances support retry, cancel, pause, resume, migrate, and go-to, individually or in bulk, with monitoring of every step and variable, durations, Service Level Agreement (SLA) compliance, dashboards, and alerts across the estate.

For details, refer to Maestro Flow.

Maestro Flow runs in Maestro Orchestrate. For the difference between Maestro Orchestrate and Maestro Automate, refer to Choosing between Maestro Orchestrate and Maestro Automate.

Correction: Release notes for Maestro Flow general availability were published on September 15, 2026 in error. The correct release date is September 17, 2026.

Conversational agents in Maestro Flow (Preview)

Maestro Flow can now model AI-powered chat and voice agents, with intent-based routing and hand-off between specialist agents. Chat nodes orchestrate real-time conversations with deterministic replies and parallel branches that run while the conversation continues, and the published flow reaches end users on the chat channels of your choice, with observability across usage metrics, execution traces, and user feedback.

Voice agents handle real-time phone calls, answering inbound calls and placing outbound ones. Audio streams to a real-time speech model, so callers can interrupt the agent mid-sentence and tools run during the call. The call transcript or a structured call summary feeds into downstream nodes.

For details, refer to the following pages:

• Chat
• Voice

Inline data entity modeling (Preview)

In Maestro Flow, you can now create and edit Data Fabric entities directly inside a VS Code solution, as a new Data Fabric entity project type alongside your Flow project. Add fields and set their types in a table-based schema editor, without leaving VS Code or configuring an Integration Service connection.

Four new built-in nodes — Query entity records, Create entity record, Update entity record, and Delete entity record — let you consume these entities from a flow without an Integration Service connection.

Two limits apply in this preview:

• Native (folder) entities only.
• VS Code only. Studio Web can open a solution containing an entity project, but can't edit the entity.

For more information, see Entities in VS Code.

Coded Functions as nodes (Preview)

A coded function can now be called from the Flow canvas as a node, so a flow can hand a step to function code instead of routing it through an intermediate workflow.

For how to author, test, and publish coded functions, refer to Coded functions.

Autopilot for Flow (Preview)

Autopilot scaffolds a flow from a description of intent, so you start from a working structure instead of an empty canvas. It is an alternative to authoring with a coding agent.

Native document processing nodes (Preview)

Document processing nodes bring UiPath document intelligence onto the Flow canvas as discrete steps, so a process can act on documents without a separate agent. The Extract node pulls typed fields from a document using a deployed UiPath Intelligent eXtraction Platform (IXP) extraction model. The Summarize node synthesizes across a document of up to 1,000 pages and returns a grounded answer with citations back to the source.

Both nodes appear in the node palette under Document processing. Because the flow calls them at a fixed point with the inputs you configure, they behave deterministically, unlike the Summarize agent tool, which an Autonomous Agent calls while reasoning.

For details, refer to Document processing.

September 16, 2026

Build a Maestro Flow with a coding agent is now generally available

Building a Maestro Flow with a coding agent is now generally available. You describe the process — routing work between people, agents, RPA, and systems with branching, approvals, and durable state — and the agent authors a runnable .flow, then helps you publish, run, diagnose, and evaluate it.

The uipath-maestro-flow skill covers the full lifecycle: authoring and validating the flow, publishing and triggering runs, diagnosing faulted runs, and building and running evaluation sets. The skill is available to install via uip skills install.

For details, refer to Maestro Flow.

September 15, 2026

Introducing evaluations for Maestro BPMN (Preview)

In Maestro BPMN processes, evaluations let you verify that a workflow behaves as expected before you publish it. You can group expected outcomes into an evaluation set and score each run against the evaluators you attach, so workflows with non-deterministic steps get regression coverage after every change. Deterministic evaluators check output exactly, and LLM-judge evaluators score meaning and trajectory.

For more information, see Evaluations.

Case Manager Agent (Preview)

In Maestro Case, you can now add an AI agent to the Case Manager so it makes orchestration decisions — starting and cancelling tasks, entering and completing stages, and escalating — for events your deterministic rules don't cover. Choose rules-first to run the agent only as a fallback, or agent-led to have it decide on every event using rules as guardrails. The agent's system prompt and input/output contract are predefined; you configure its model, context, memory, tools, and escalation paths, and test it with evaluations before deploying.

For more information, see Configuring and testing the Case Manager Agent (preview).

Build a Maestro Case with a coding agent (Preview)

You can now build a Maestro Case using the coding agent of your choice — Claude Code, Codex, GitHub Copilot, Cursor, or Jules. Describe the case, hand over a BPMN model, a process map, or an existing PDD, and the agent proposes a case plan for your approval before it builds, debugs, and deploys the case plan and its tasks in your solution.

The uipath-maestro-case skill covers the flow end to end: it proposes the stages, tasks, transition rules, and Service Level Agreements (SLAs), walks you through one review before building anything, then authors, validates, and publishes the case definition. The skill is available to install via uip skills install.

For more information, refer to the following pages:

• Build a Maestro Case with a coding agent (preview)
• Maestro Case
• UiPath for Coding Agents — Install and set up
• UiPath for Coding Agents — September 2026 release notes

September 10, 2026

Close case instances through the CaseApp API

In Maestro Case, a new POST instances/{instanceId}/close endpoint on the v3 CaseApp API lets you close a running case instance, authorized via the Cases.Close persona grant. Closing a live instance transitions it to Canceling while the worker completes the shift to Cancelled asynchronously; an already-terminal instance returns its current status unchanged, and a completed instance is rejected rather than cancelled to protect any standby workflow a later reopen depends on.

For more information, see CaseApp requests.

Attach a payload when triggering an ad hoc case task

In Maestro Case, the POST /v3/caseapp/instances/{instanceId}/tasks/trigger endpoint now accepts an optional taskInput object alongside the task name. The free-form JSON object is forwarded verbatim to the triggered task as a nested payload, enabling callers to pass data such as approval references or decision payloads at trigger time. Omitting it leaves the request behaving exactly as before.

For more information, see CaseApp requests.

Bug fixes

• Maestro BPMN: Process instance migrations that would remove an element where a user-cancelled activity is waiting are now correctly rejected, bringing cancelled elements in line with faulted elements as protected migration anchors.
• Maestro BPMN: A Send Task node's connection override applied at release time through a binding is no longer ignored in favor of the design-time connection.
• Maestro BPMN, Case, and Flow: The Action history tab now logs an entry when an instance — deployed or in a debug run — becomes throttled due to high activity volume, so you can see when and how often it was affected. For more information, see Debugging.

September 3, 2026

Configure and manage MCP tools directly in Flow

In Maestro Flow, Autonomous Agent nodes now support richer control over Model Context Protocol (MCP) tools. You can edit per-argument descriptions, view a tool's full input and output schema, and choose how each argument gets its value: the agent decides at runtime, it's bound to an agent variable, or it's a fixed value that can be marked sensitive. MCP servers now also expose an explicit Refresh tools action instead of only discovering tools automatically, and can pull their tool list live from Agent Hub.

For more information, see Agent.

Keep MCP tool schemas up to date automatically

MCP (Model Context Protocol) tools added to an Agent node in Maestro Flow can drift out of date if the underlying MCP server's tool definition changes after you configure it — for example, a parameter gets renamed or added.

A new Refresh schema before call toggle, in the tool's configuration panel and on by default, checks the MCP server for the tool's current schema right before each call, so the workflow keeps working even if you never refresh it manually. When disabled, the tool always uses the schema you configured, which is faster and more predictable if the server's tools rarely change. The setting is saved with the workflow and survives closing and reopening the project.

For more information, see Agent.

Trigger ad-hoc case tasks through the CaseApp API

In Maestro Case, a new POST /instances/{instanceId}/tasks/trigger endpoint on the v3 CaseApp API lets you manually start an ad-hoc task on a running case instance by supplying its case-plan task name. Access requires the Cases.RunAdhocTasks permission scoped to the stage that owns the task. Task name matching is case-sensitive, and only tasks with an "adhoc" entry condition in the case plan are eligible — other names return a 404.

For more information, see CaseApp requests.

Bug fixes

• Maestro BPMN: =js: expressions used as Data Fabric query filter values are now evaluated before the query is sent, so dynamic values resolve correctly instead of being passed through as raw expression strings. For more information, see Data Fabric operations.
• Maestro BPMN: The Get queue items activity no longer fails on Orchestrator tenants with the Strict OData API setting enabled. For more information, see Queue task activities.
• Maestro BPMN: Multi-instance elements with large marker input collections no longer fail during execution. For more information, see Markers.
• Maestro BPMN: A Studio Web debug run against an empty queue now returns a 404 (user error) instead of a 500 (system error); deployed runs are unaffected.
• Maestro Flow: Evaluation output evaluators (such as Exact Match) are now pre-selected and pre-filled with the shared expected output entered in the evaluation wizard. For more information, see Evaluations.
• Maestro Flow: The MCP server picker in the add-node panel now loads all available servers instead of stopping at the first 100. For more information, see Agent.