UiPath Documentation
maestro
latest
false
Maestro Orchestrate release notes
  • Automation Cloud and Test Cloud
    • 2026
      • November 2026
      • October 2026
      • September 2026
      • August 2026
      • July 2026
      • June 2026
      • May 2026
      • April 2026
      • March 2026
      • February 2026
      • January 2026
  • Automation Cloud Dedicated and Test Cloud Dedicated

October 2026

October 2026 release notes for Maestro Orchestrate in Automation Cloud and Test Cloud.

October 30, 2026​

Maestro Flow: Extraction models built in Flow, and the Validate extraction node (Preview)​

In Maestro Flow, the Extract node can now create an Intelligent Xtraction and Processing (IXP) model that you build, evaluate, and run in the node, without leaving Flow. The Extract document option creates the model, and its taxonomy, configuration, and validated predictions are all set up on the canvas. A model built in one flow can be reused in another flow of the same solution, and, after you deploy it with its solution, in flows of other solutions.

Models built in Flow can also be consumed from public APIs and activities. IXP in Flow is in Preview.

The new Validate extraction node, in the Human category, sends the output of an Extract node to a person, who checks and corrects the extracted data before the run continues. Validate extraction works only with Extract nodes created in the same flow with the Extract document option, not with nodes bound to a published model or to a model from another flow.

For more information, refer to the following pages:

Maestro Flow: Error handling on Quick Form nodes​

In Maestro Flow, the Quick Form node now supports error handling. When the node fails, the run can continue on the node's error path instead of stopping.

For more information, refer to Error handling.

Maestro Flow: Phone numbers in the call context, and no escalations on the Voice agent (Preview)​

In Maestro Flow, the callContext output of the Incoming call trigger and of the Create Outgoing Call node now includes the number the call came from (from) and the number that was called (to), so you can route or log calls by phone number. For an incoming call, from is the caller and to is your connected number. For an outgoing call, from is your connected number and to is the number you call.

The Voice agent node no longer has an Escalations connection, because a call can't wait while a person completes a task. A person can act on the outcome of a call through a node from the Human category placed after the Voice agent. The Voice agent node is in Preview.

For more information, refer to the following pages:

Maestro BPMN and Maestro Case: Missing required variables block debugging​

In Maestro BPMN and Maestro Case, a required variable that is missing on an activity, task, or case stage is now a critical issue that blocks both publishing and debugging. Previously, it blocked publishing but still let you start a debug run.

Maestro BPMN: Retry settings checked against supported ranges​

In Maestro BPMN, new element-level retry settings are now checked as you enter them. Max retries must be between 1 and 10, the initial delay between 1 second and 1 hour, and the exponential base between 1 and 5, and retries can span up to 24 hours in total. Values outside these ranges show an error in the form and in the Issues panel. Existing retry settings are kept as they are, and out-of-range values are reported instead of being changed.

For more information, refer to Properties panel.

Maestro BPMN: Arguments on connector-triggered start events​

In Maestro BPMN, start events triggered by a connector event, such as Email Received, now show an Arguments section in the Properties panel, where you can add, edit, and remove process arguments, as you already could on queue start events. Previously, you could create these arguments only from the Data Manager.

For more information, refer to Events.

Maestro BPMN: Business rules action selected by default​

In Maestro BPMN, adding a Business rule task from More elements, or changing an element into a Business rule task, now selects the Business rules action by default. Business rule tasks added earlier keep an empty action until you select Business rules.

For more information, refer to Business rule task.

In Maestro Case, task links on a case instance now open the task in the Case app instead of Action Center.

For more information, refer to Case app.

Maestro BPMN and Maestro Case: Faster instance pages​

In Maestro BPMN and Maestro Case, opening an instance now reuses the diagram already downloaded for its package version, so moving between a process page and its instances, or between instances of the same version, loads the canvas faster.

Bug fixes​

All canvases​
  • Opening a BPMN, Case, or Flow instance that you don't have permission to view, or that doesn't exist, now shows a Can't find it page instead of loading indefinitely.
Instance management​
  • Removing several instances now tells you when some or all of them couldn't be deleted, instead of always reporting success.
Maestro BPMN and Maestro Case​
  • Selecting a node, a connection, or an empty area of the canvas now reliably brings back the Maestro Properties panel after you open the Studio Web properties panel.
  • Debug runs now start in the folder selected for debugging in Studio Web, instead of your personal folder or a previously used folder, and the folder is cleared when the debug session ends.
  • Selecting an element during a debug run in Studio Web no longer crashes the Details panel.
  • Incident log messages in the debug panel now include the element's name when one is available, instead of only its ID.
  • Orchestrator assets created from the Data Manager now keep their type in the variable picker, such as text, number, Boolean, or credential, instead of appearing as untyped objects.
  • When you switch an Orchestrator variable to a new asset created in place, the variable and its inputs now follow the new asset. Accessing an asset that isn't a credential through .username or .password now shows a validation issue.
  • Editing a JSON (Object) or array-of-objects variable or task output now shows its schema below the value, as for JSON arguments.
  • After you pick a variable in a field, the variable list no longer opens again and covers the fields below it.
  • The variable picker no longer lists Method, Body, Code, Raw body, and Request under an HTTP request's response body or headers, because expressions built from them were always empty at runtime.
  • Edits to connector activity fields are no longer reverted while the activity shows a validation error.
  • Connector activities keep their configured connection while the solution resources are still loading.
  • An Integration Service activity's outputs, including Error, no longer disappear from the Properties panel when you select another element and then return to the activity.
  • Adding or changing a process, agent, or app that a diagram uses no longer discards unsaved edits in the open diagram or resets the selected element. Processes and agents picked from the canvas toolbox are now packaged with their type, as when picked in the Properties panel.
  • Processes and case plans that use error boundary events can now be packed into a solution with the UiPath CLI, without having to reopen and save them first.
  • Skeleton loaders, variable chips in expression and variable fields, and hovered elements in the instance element filter are now readable in the Modern dark theme.
Maestro BPMN​
  • The canvas can no longer be edited while a debug run is starting. Previously, a change made during startup was saved to the file but not included in the run.
  • Picking a published action app from the canvas + toolbox now adds it to the solution, as picking it in the Properties panel does. When a resource picked from the toolbox can't be added to the solution, a message now explains why, and no broken node is left on the canvas.
  • Validation error and warning tooltips on nodes are no longer hidden behind the node toolbar and connection buttons.
  • Adding an In/Out argument of type Object no longer shows the argument's schema as the end event's value. Adding or editing an argument in a reopened process no longer resets the schemas of the other arguments or the values their end events pass out.
  • Script task outputs in the Properties panel now show readable labels, such as Script response instead of scriptResponse. Variable names and saved processes don't change.
  • In the C# expression editor, an error from generating an expression with Autopilot no longer overlaps the editor.
  • In Classic Autopilot, the diagram no longer disappears after you accept a generated diagram on the canvas and then in the Autopilot panel. Accepting or rejecting on the canvas now also updates the Autopilot panel.
Maestro Case​
  • Case role permissions now refer to manually triggered tasks instead of ad-hoc tasks.
  • Task assignees in the Case app now see the floating Save button on open tasks, and completed tasks no longer show it.
  • The Assignee filter on a case's Tasks tab now lists only the people assigned tasks in that case, lets you type to find one, and shows their tasks instead of an empty list.
  • Case app links that lose their folder, for example after a refresh or when copied into a new tab, now open the case instead of showing a "Data retention has expired" message.
  • Case entity and Data Fabric variables in the JSON code view of a case app section now save correctly. Section details whose JSON doesn't parse show "Invalid JSON format" and can't be saved.
  • Case files with a newer patch version within the supported major and minor version now open unchanged instead of being rejected.
  • Variables related to case tasks are now kept at the process level when the case is saved, so they stay available from the process scope instead of moving to a task-level location.
Maestro Flow​
  • Opening a child Flow from its parent's run details now shows the Flow instance view instead of the BPMN one.

October 22, 2026​

Maestro: End-to-end traces for external agent calls​

When a Maestro process invokes an external agent — running in a platform such as Azure AI Foundry or Databricks — you can now trace the call end to end.

Maestro participates in distributed tracing using the open W3C Trace Context standard: every external agent call carries a shared trace ID, so an agent that supports the standard records its own steps — model calls, tool use, latency, and errors — under the same trace.

Once you configure Data Export to your observability platform, Maestro spans and the external agent's spans stitch into a single end-to-end view that you can search by trace ID.

For more information, refer to External agent traces.

Correction, November 3, 2026: This feature was released on October 22, 2026, but was not included in the release notes at the time.

October 13, 2026​

All canvases: Consistent names for Maestro BPMN, Maestro Case, and Maestro Flow​

Designers, task pickers, properties, and validation messages now consistently use the names Maestro BPMN, Maestro Case, and Maestro Flow, instead of Agentic process, Case management, or Flow. Maestro Flow is no longer labeled as a preview feature.

Maestro BPMN and Maestro Case: Property bindings for wait-for triggers and connector activities​

In Maestro BPMN and Maestro Case, wait-for triggers and connector activities now keep their property-level bindings when you save, publish, and reopen a project, including configuration values used inside filter expressions.

Maestro BPMN: Build and Evaluate switch in the canvas toolbar​

In Maestro BPMN, the Build and Evaluate choice is now a dropdown at the start of the bottom canvas toolbar. In Studio Web, Maestro BPMN designers also get an Add node action in the bottom toolbar.

For more information, refer to Modeling your process.

Maestro Case: Discover the ad-hoc tasks you can trigger on a case​

In Maestro Case, a new GET /v3/caseapp/instances/{instanceId}/tasks/adhoc endpoint lets callers discover which ad-hoc tasks they can trigger on a case instance, grouped by stage. The endpoint requires only the Cases.RunAdhocTasks permission, so callers no longer need the broader Cases.ViewSummary permission just to see which tasks are available. A task name returned by this endpoint can be passed directly to the existing trigger endpoint.

For more information, refer to CaseApp requests.

Maestro Case: Runtime stage states and badges​

In Maestro Case, instance views now show which stages can end the case and which one did: an Ends case badge becomes Ended case on the stage that ended it. Stages cut short by a failed task or by the case ending now show Failed or Terminated instead of staying in progress, on the canvas and in the case app.

For more information, refer to Case instances.

Maestro Case: Case roles improvements​

In Maestro Case, the Case JSON editor now lists case-role problems, marks them on the relevant lines, and disables Save until they are fixed. The case roles dialog asks before discarding unsaved changes, groups role actions with a select-all checkbox per group, and has a clearer layout.

Maestro Flow: Bring-Your-Own Guardrail configuration name on the guardrails palette and list​

In Maestro Flow, Bring-Your-Own Guardrail (BYO) entries in the add-guardrail palette and the agent guardrails list now display the tenant's configuration name instead of the connector's generic validator label, making it easier to identify which configuration is applied. A BYO badge appears beside the guardrail name in both views, with the guardrail provider name shown beneath it. Dialog titles for adding or editing a BYO guardrail reflect the configuration name as well.

For more information, refer to Agent.

Maestro Flow: Debug and create options in VS Code​

In Maestro Flow, the VS Code extension now disables Debug while a project has issues that prevent debugging, with a tooltip explaining that all issues must be cleared. The add-item pickers on the canvas offer Create new options again, so you can create a process or resource directly from the picker.

For more information, refer to Flow in VS Code.

Bug fixes​

  • All canvases: Elements in Studio Web outside the Maestro Orchestrate designer no longer disappear while a BPMN, Case, or business rules canvas is open.
  • All canvases: Data grids now remember their page size and current page when you navigate away and return.
  • All canvases: The Create element panel now stays inside the canvas when a bottom panel reduces the available space.
  • All canvases: Solution resource references are checked again when the solution's resource list changes, so resources that become available no longer show stale errors or block Debug.
  • Maestro BPMN and Case: Solution-installed action apps that use semantic versions now load their human-task actions correctly.
  • Maestro BPMN and Case: Connector activity properties now warn when the host goes offline after the configuration has loaded.
  • Maestro BPMN and Case: The Select activity picker now stays visible within the properties panel and opens directly on the connector of the activity you are replacing.
  • Maestro BPMN and Case: Bindings to deployed processes in another folder now show their folder, and same-name solution projects produce a non-blocking warning instead of being confused with them.
  • Maestro BPMN and Case: Integration Service activities created with the older activity designer now show their outputs in the same Outputs section as newer activities.
  • Maestro BPMN: When an activity input is a JSON object containing secret values, only the individual secret fields are now masked in API responses instead of the entire payload, and secrets are always masked regardless of the caller's permissions.
  • Maestro BPMN: Renaming a variable named response, such as the default output of a Download File or Integration Service activity, no longer breaks the output of script tasks. Affected processes are repaired when you open them in the designer; republish them so running processes get the fix.
  • Maestro BPMN: Picking a variable into a C# expression now inserts a valid C# path, without JavaScript-style optional chaining.
  • Maestro BPMN: Dragging nodes on the canvas is more predictable: nodes that can't be dropped where they land turn red and return to their starting point, including when several nodes or a sub-process are dragged together.
  • Maestro BPMN: Swimlanes now stay inside their pool when the pool is resized or grows.
  • Maestro BPMN: Sequence flows in diagrams with pools or lanes can be selected again, instead of selecting the lane.
  • Maestro BPMN: In the Data Manager, editing an Object or Array variable created from activity outputs no longer clears its value, and renamed nested properties keep the name you typed.
  • Maestro Case: The case plan endpoints now return a 400 with error code CasePlanNotCaseManagementInstance when called on an instance that isn't a case management process, instead of failing with a 500.
  • Maestro Case: Callers authorized only through Case role-based access control can now view case summaries, select stages, and trigger case tasks through the v3 CaseApp API, without also needing Orchestrator package permissions.
  • Maestro Case: The start time shown for a new case element now matches when the element actually started, instead of a slightly later time.
  • Maestro Case: A case task that is already running is no longer started a second time when the same event triggers it again.
  • Maestro Case: Case-role validation is now consistent between the roles dialog and the issues panel.
  • Maestro Case: Older case files whose Update Variables entries point to the wrong task are now repaired automatically, and cases whose Update Variables entries only refer to each other no longer fail to open.
  • Maestro Case: Case files with positions for only some nodes now open instead of crashing the canvas.
  • Maestro Case: Uploaded documents keep their Last modified and Date uploaded values, previews detect common file types from the extension, and the version column is removed from the documents list.
  • Maestro Case: Case comments now require text before you can post them, even with an attachment.
  • Maestro Case: The variable picker shows the current names of renamed case triggers.
  • Maestro Case: Event subprocesses in a case now receive the current values of variables reassigned from task outputs or produced by triggers.
  • Maestro Case: Selecting a rule-expression issue now opens the related rule section in the properties panel.
  • Maestro Case: Placeholder connector rules now show a validation error and can't be debugged until configured.
  • Maestro Case: Reserved-variable-name issues on case tasks now show the task's display name.
  • Maestro Case: Bulk migration is now available for running case instances.
  • Maestro Flow: Maestro Automate runs no longer show actions available only in Maestro Flow, such as pause, resume, migrate, or go to.

October 7, 2026​

Build a BPMN with a coding agent (Preview)​

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

The uipath-maestro-bpmn skill covers the flow end to end: it proposes the events, tasks, gateways, sequence flows, and participants, walks you through a review before building anything, then authors, validates, simulates, and publishes the process model. The skill is available to install via uip skills install.

For more information, refer to the following pages:

Was this page helpful?

Connect

Need help? Support(opens in new window)

Want to learn? UiPath Academy(opens in new window)

Have questions? UiPath Forum(opens in new window)

Stay updated