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

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.

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.

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.

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.

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.

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.

For more information, refer to Implementing stage-level personas and permissions.

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.

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.

You can now build a Maestro 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: