March 2026

March 4, 2026

Configure error handling per node

You can now configure how each node handles errors using the Error mapping property in the properties panel. Each mapping has three fields:

• Error: Select from the list of errors defined for the process, or create a new error inline using the menu button. Errors are defined at the process level and linked to the mapping.
• Condition: Use the variable picker to define when the mapping applies. You can write the condition in JavaScript or C#.
• Details: Add a description for the mapping.

To change the order in which Maestro evaluates mappings, drag them to reorder by priority.

Event subprocess defaults to error start event

When you add an event subprocess to the canvas, it now defaults to an error start event instead of a message start event. This removes the extra step of manually changing the start event type for the most common error-handling use case.

Warnings for invalid expressions

Maestro now shows a warning when an expression is invalid, both when you save it and during execution. Previously, invalid expressions were saved silently and did not produce errors at runtime, making it difficult to identify the source of unexpected behavior.

Combined output for Loop nodes

The Loop node now generates a combined output that aggregates the results from all iterations into a single collection. Variables inside a loop are scoped to each iteration, keeping each cycle's data isolated.

You can use the combined output directly in downstream steps without additional data transformation.

DataFabric field-based queries

You can now query DataFabric entities by field value using the qes: prefix syntax:

datafabric.EntityName["qes:FieldName=Value"].FieldToRead

For example: datafabric.LoanApplicationCase["qes:CaseId=HL-999"].LoanAmount

Previously, entity lookup required an internal record ID known in advance.

Automatic DataFabric entity updates

Activity outputs that target a DataFabric entity using the target="=datafabric.EntityName[...]" syntax are now automatically written back to the entity after the activity completes. This enables variable update flows to integrate with DataFabric without additional configuration steps.

Agent debug jobs during debugging

When you debug an agentic process, Maestro runs an agent debug job and uses your free debug credits, reducing consumption of standard agent credits during testing.

Variable IDs now update on rename

Renaming a variable now updates the variable ID to match the new name. Previously, the ID stayed fixed after a rename, which caused confusion when expressions still referenced the original ID or when newly renamed variables had numbers appended to their IDs.

Note:

After renaming a variable, expressions that referenced the old ID will break. Use the Fix variables dialog to identify and update any broken references.

Variables and subprocess scope

Moving nodes into or out of subprocesses replaced variable IDs with result.response when outputs reinitialized, which caused conflicts from orphaned entries. Maestro now preserves variable IDs when you move nodes between scopes and removes duplicate outputs.

Deprecation of C# expressions

C# expressions now display a deprecation warning that includes the planned removal date. JavaScript is the recommended expression language for all new Maestro development. The feature flag for JavaScript as the default expression language is now enabled.

Bug fixes

Modeling and canvas behavior

• Improved edge positioning when no waypoints are defined, so connectors align correctly with node layouts.
• Fixed boundary events on subprocesses so they reposition correctly when the container expands.
• Resolved multiple swimlane rendering issues, including disappearing sequence flow names and labels overlapping edges.
• Boundary timer events now support recurring execution with configurable repetitions, and timer behavior aligns with intermediate timer events.

Variables and data handling

• The variable picker now includes collaboration-level variables, ensuring correct variable selection across scopes.
• Deleting a node or variable that is referenced elsewhere now triggers a warning.
• JavaScript expressions no longer allow assignment operators (=); use equality operators (== or ===) instead.
• Validation no longer shows false warnings when a variable references another variable defined on the same node.
• Deleting an argument in Data Manager now persists correctly and no longer appears in debug prompts after removal.

Execution and debugging

• The debug execution panel in Studio Web no longer jumps while scrolling, making execution results easier to review.
• Manually invoking an event trigger entry point now shows a clear message that event trigger entry points cannot be invoked manually.

UI and navigation

• Resizing the properties panel no longer disables the collapse or expand button.
• The Maestro landing page now loads instances correctly for accounts with more than 20 agentic processes.

Integrations

• Integration Service LIST operations now use the correct HTTP method, preventing request failures.