July 2026 release notes for Maestro in Automation Cloud.

In Maestro Case, Case Manager decision trace spans now include a zero-based index indicating which chaining cycle produced each decision and an ordered list of the events that led to it. This information helps you reconstruct the sequence and causal path of decisions made during a case.

For more information, see Introduction to Maestro Case.

In Maestro BPMN, Integration Service Send tasks now support URL values in query parameters. Maestro encodes these values before sending them so that the connector receives them without corruption or rejection.

For more information, see Send task.

In Maestro Flow, running a single node in the VS Code extension now shows a live execution trace in the execution panel, matching the experience already available in Studio Web. The trace includes span timings, variable inputs and outputs, and error details for the node that ran.

When you trigger a single-node run, the execution panel expands automatically and shows a loading indicator through the preparation and deployment stages. Once the execution instance is active, the panel switches to the live trace.

For more information, see Debugging basics.

In Maestro Flow, code editors in the properties panel can now be resized vertically. An Expand editor button opens the editor in a larger dialog, providing more room to write or review complex expressions and scripts.

In Maestro Flow, pasting nodes directly into an empty Loop container now automatically resizes the loop and connects the pasted nodes to the loop body.

Maestro Flow is a new canvas for building lightweight business orchestration in UiPath. Flow brings agents, API calls, human-in-the-loop steps, document processing, and system actions together into a single workflow.

Maestro Flow runs in Studio Web and in the VS Code extension. Flow offers a visual design canvas, real-time debugging as a workflow runs, one-step deployment, and run inspection down to the individual node.

For more information, see the Maestro Flow documentation.

Data Fabric operations — read, create, update, upsert, and query — now work with composite entities. Previously, operations targeting composite entities failed silently or returned errors.

For more information, see Data Fabric operations in Maestro.

In Maestro Business Process Model and Notation (BPMN), Data Fabric expressions can now reference process bindings and variables dynamically for both the entity name and the folder path. Previously, the entity name and ?folderPath= segment in a datafabric[...] expression had to be literal strings.

Now they can be binding or variable references resolved at runtime against the workflow's variable store — for example, =datafabric[bindings.EntityName?folderPath=bindings.FolderKey][...].

For more information, see Data Fabric operations in Maestro.

The Agentic Orchestration (AO) DataPipe event payload for process instances now includes a ProcessType field indicating whether the instance is a ProcessOrchestration or CaseManagement process. This lets downstream consumers of the DataPipe stream distinguish process kinds without additional lookups.

In Maestro BPMN, cancel, pause, and resume signals sent to a parent process instance now propagate to any active embedded subprocess child workflows. When a parent is paused, the instance status transitions to "Paused" only after the nested subprocess confirms it has quiesced — matching the expected timing.

Resume propagation works symmetrically. Cancelling a parent while a subprocess is in-flight suppresses all downstream elements that would have run after the subprocess completed.

For more information, see Subprocesses and modularity.

In Maestro BPMN, the GoTo operation now supports redirecting execution to an element inside a currently running subprocess. The operation routes the transition to the active child subprocess workflow when the source and target elements belong to the same subprocess scope. Transitions that cross subprocess boundaries remain unsupported.

In Maestro Case, the RetrieveCaseState activity response now includes a tasksCompletedV2 field alongside the existing tasksCompleted field. Each entry in tasksCompletedV2 carries both an identifier and a name, using the same identifier format as entries in tasksRunning.

The original tasksCompleted list is unchanged for backward compatibility. tasksCompletedV2 is only populated when the V2 case-management schema is in use.

For more information, see Introduction to Maestro Case.

In Maestro BPMN, when migrating a running instance to a new package version, the variable diff endpoint now returns all InOut working variables — including subprocess-scoped variables and activity output variables — grouped by scope and kind.

Supplied values on the upgrade request overwrite existing carried values and are forwarded to running subprocesses so their isolated variable scopes are updated.

For more information, see Publishing and upgrading agentic processes.