Maestro release notes

Last updated Feb 19, 2026

February 2026

February 19, 2026

Improved RBAC validation for Data Fabric triggers

Maestro now relies on stricter Data Fabric RBAC validation for trigger event delivery. If a workflow no longer starts or receives incomplete event data, review the permissions of the user configured in the trigger connection.

For details, see the Data Fabric release notes

February 18, 2026

Support for event subprocesses

Centralize error and message handling across your process by leveraging event subprocesses in the BPMN canvas. Instead of managing errors through multiple boundary events or routing message handling through the main flow, you can group related scenarios into a single BPMN element.

For example, rather than attaching the same error boundary event to multiple tasks, you can implement the error handling in an event subprocess that is triggered when that common error is thrown.

Execution trail export

You can now export full execution trail of a BPMN process in a JSON format. After running or debugging your BPMN process, the Execution trail panel populates with data about the steps, such as event names, LLM calls, or trace IDs. To export this data to your device, select the Download icon.

New property for the Script task

The Script task has a new property: Update variables. This property allows you to select a pre-defined variable and update its value in the script.

At runtime, the Script task uses the variable value assigned in the Update variables property. You can also set expressions.

Clearer entrypoint selection in Orchestrator

Display names of start events now show up in the Orchestrator process configuration step, where you need to select an entry point. You can identify the start event you want to use by the following syntax: filepath#displayname. For example, process.bpmn#wait_for_mail.

Tidy up the nodes on your canvas

Keep your canvas organized and easier to read by automatically rearranging your BPMN nodes. Select the elements you want to rearrange, right-click and choose Tidy up selected nodes, or apply it to your entire canvas with the Tidy up nodes option.

February 13, 2026

Bug fixes

Modeling and canvas

Sequence flow edges overlapped labels on the canvas, which caused text to render under connector arrows. Labels now display clearly and maintain proper spacing from edges.
The canvas allowed editing actions in read-only mode. The Delete button and context menu options no longer appear when the model is not editable.
Variables retained the original scope after moving a node into or out of a subprocess. Maestro now updates variable scope automatically to match the new node location.

Variables and validation

The variable picker showed the same generated name for different task outputs, which made variables appear identical in editors. The editor now displays unique variable identifiers so you can select the correct variable.
Filtering by global variables did not return results in Instance Management. Global process-scope variables now propagate correctly to Insights, and filters apply as expected.
Error events did not require a defined code or name during parsing. Maestro now validates error definitions before execution and flags missing values early.

Execution and integrations

The JSON editor did not persist array or object inputs for the connectors fields. You can change the data type from null to array or object and save the value without it reverting.
The JSON editor switched modes without user action. The editor now stays in the selected mode until you change it.
Improved performance in the JavaScript Editor. You can now open the editor and save variable expressions without delays.
Triggers created during solution deployment mapped to the same entry point in a project. Each trigger now links to the correct start event.
User tasks copied inputs into outputs even when no outputs were defined. Inputs and outputs now remain separate, and runtime expressions evaluate correctly.

February 11, 2026

Introducing data residency in Switzerland for Maestro

As part of our ongoing cloud expansion, we’re bringing complete data sovereignty to the Switzerland region for Maestro. This ensures your data is securely stored and replicated across multiple availability zones within Switzerland, offering full control and compliance confidence.

For details, refer to Data residency in the Automation Cloud Admin guide.