Maestro release notes

Autopilot™ for Maestro (Developers) is now generally available, helping you design and evolve BPMN workflows faster by turning natural-language prompts and documents into automation-ready models.

You can use Autopilot to generate an initial BPMN model from a written description or supporting files, then refine it iteratively without manually constructing every element. Models are streamed to the canvas incrementally, allowing you to review and adjust the structure as Autopilot creates it.

Autopilot also provides contextual design-time assistance, including guidance on BPMN concepts, UiPath capabilities, and help with writing C# and JavaScript expressions used in tasks such as Script tasks. All interactions are centralized in a single panel that preserves conversational context across iterations.

For more information, see the Maestro user guide.

Maestro now supports file arguments and variables using the new JobAttachment type, so you can pass files into a process as input arguments, generate files as output arguments, and reference attachments directly in expressions and variables.

File handling in Data Fabric no longer requires creating custom entities just to store file data. Files can be managed directly as first-class resources without creating custom entities.

You can now hover over any element on the canvas to see its validation issues, making configuration problems easier to discover and resolve.

Copy-and-paste on the BPMN canvas is more reliable for agentic processes, and a Paste option has been added to the context menu.

You can add elements to the canvas by double-clicking them in the left toolbar, which reduces reliance on drag-and-drop interactions.

The minimap is now available behind a show/hide control, which reduces visual clutter while modeling complex diagrams.

You now have better visibility into how processes execute across boundaries. Child-instance spans are displayed in the Execution Trail, allowing you to follow execution end to end across parent and child processes.

Instance identification and timing are also easier to track. You can define a custom instance ID using an expression evaluated at runtime, making instances easier to recognize. For timer-based workflows, Maestro now shows countdowns for active timer events, so you can see how much time remains before a timer triggers.

On the Maestro homepage, Studio Web solutions now display their status (Draft, Published, or Deployed), helping you quickly identify which solutions are ready for use.

Configuring workflows is now safer and more predictable. You can select action catalogs using a resource picker, reducing the risk of referencing incorrect or unavailable resources.

Maestro also handles variables more reliably when you modify a workflow. Variable identifiers are now more stable, validation is clearer when variables are deleted or renamed, and invalid references are easier to reconcile. This reduces rework when reorganizing tasks or iterating on existing processes.

Connectors no longer stay highlighted after dragging elements across the canvas.

You can now delete swimlanes without removing the entire participant, and child elements are preserved.

Multi-instance markers now consistently display the iterator item in the expressions editor.

Pasted subprocess elements now appear in the correct location after reload.

Integration Service validation errors now surface correctly in the Validation issues panel.

The variable picker now suggests only compatible variable types.

Script Task input arguments can now be renamed without losing changes.

JSON values in the Monaco editor now load with proper indentation.

End events inside subprocesses now display their values as Outputs instead of Arguments.

Output variable evaluation now works correctly for subprocesses ending with an Error end event.

Fixed an issue where validation incorrectly reported that a variable was not set even when a value had been assigned.

Fixed a validation error that flagged Double and Float variables as incompatible with agent inputs of type Number. These values now validate correctly and behave as expected at runtime.

Fixed an issue where renaming a filter variable did not save correctly and the old name continued to appear. Filter variable names now update correctly, and duplicate names are no longer allowed.

Fixed an issue where the All option in the date range picker did not return the full dataset as expected.

Fixed an issue that caused duplicate instances to appear in the instance list.

Fixed an issue where the Execution Trail did not show element names for steps executed inside a Call Activity. Child-instance elements now display their correct names so you can follow the full execution flow.

Maestro now loads large datasets more reliably. This update improves performance for the Processes table on the homepage and for Execution Trails with many events.

You can now use Autopilot™ for Maestro (preview) to convert common document and image formats into BPMN diagrams, which reduces the effort required to create an initial model. Read more in the Maestro user guide.

We improved information extraction for Autopilot BPMN document processing, which results in more accurate BPMN structures and higher-quality models.

We added support for event subprocesses on the BPMN canvas, which includes the ability to add or convert subprocesses and configure a single start event.

Added a Transitioning filter and an All date-range option, making it easier to track instances across all states.

We updated the Instance Management header for clearer navigation and improved visibility of key instance metrics.

We updated date and time displays in Instance Management to show local device time by default, with UTC time visible on hover.

The Script Task now displays the scriptResponse output in the standard output format instead of the JSON schema editor. You can still access the JSON schema view from Settings.

We added support for output arguments larger than 500k characters.

We improved error handling so that internal JSON decoding errors are no longer displayed to end users.

Maestro now synchronizes paused and faulted instance statuses with Orchestrator. Orchestrator displays Paused instances from Maestro as Suspended (manual) and Faulted instances as Suspended (with errors).

We improved the variable picker so it now closes automatically after selecting a variable.

This release brings accessibility improvements and security updates and patches to address Common Vulnerabilities and Exposures (CVEs).

We fixed an issue where clicking the end of an element edge caused the edge to disappear during an incomplete reconnect action.

We resolved multiple copy-and-paste issues on the BPMN canvas, including problems pasting activities in agentic processes and situations where paste failed after deselecting all elements.

Fixed an issue that previously placed annotations outside of swimlanes. Now, swimlanes are ignored for annotation positioning.

We fixed an issue where dragging nodes inside a subprocess could unintentionally select the subprocess.

We fixed an issue where variables from the start event appeared twice in IntelliSense. Only the correct, implicit output variable is now shown.

We fixed an issue where variable replacement in expressions incorrectly matched partial variable names, resulting in unintended substitutions.

We fixed an issue where clicking between Integration Service nodes caused multiple nodes to become selected.

We fixed an issue where email trigger debugging in Maestro did not consistently select the latest email, resulting in behavior that differed from RPA debugging.

We standardized Integration Service error messages to ensure consistent formatting and clearer guidance across all response types.

We fixed an issue where dependencies, such as waiting or trigger jobs, were not cleaned up when a Maestro process was canceled or stopped.

We fixed an issue where file outputs from agents were not correctly recognized in Maestro, preventing them from being used in downstream activities such as email attachments.

We fixed an issue where the Open job button did not appear in the Execution trail for agent jobs.

Fixed a Firefox-specific issue where Maestro did not save custom filter values when you used Firefox.