- Automation Cloud and Test Cloud
- Automation Cloud Dedicated and Test Cloud Dedicated
November 2026
November 2026 release notes for Maestro Orchestrate in Automation Cloud and Test Cloud.
November 13, 2026
Case and BPMN: New connector configuration experience
In Case and BPMN, every Integration Service connector item you add now opens in a new configuration experience, where you select the activity first and then the connection. This covers case tasks and rules, connector activities, triggers, and external agents and automations, including items you add to existing cases and processes. Existing items keep the previous experience and show a message that a newer version is available. To upgrade an item, remove it and add it again.
The new configuration experience is available in Automation Cloud and Test Cloud only, not in Automation Suite.
For more information, refer to Connector configuration experience.
November 11, 2026
Case: Case app (Modern) (Preview)
Case in Maestro Orchestrate now offers Case app (Modern), a new case app type you can choose for a case plan, alongside Case app (Legacy) and a custom app built with the TypeScript SDK. Case app (Modern) opens as its own site, with a modern design and Case Persona permissions: pages and actions are scoped to each user's Case role, instead of being visible to everyone in the tenant.
Case app (Modern) also adds:
- Apps that group one or more case processes under a shared name, icon, and color.
- An AI-generated case summary.
- A conversational agent panel scoped to the open case.
- A dedicated SLA tab.
- A stage board with planned tasks.
- A top-level Actions inbox for tasks across cases.
Case roles can also grant the Manage permission again, listed under Administer in the Case roles dialog. Manage covers publishing and unpublishing case definitions, and it can only be granted on the whole case.
Case app (Modern) is in Preview.
For more information, refer to Case app (Modern) and Case app (Modern) permissions reference.
Flow: Match all cases on the Switch node
In Flow, the Switch node has a new Match all cases option. When it's on, every case whose condition is true runs its branch. The option is off by default, so existing Switch nodes keep taking the first match. A Merge node placed after the Switch node waits only for the branches that ran.
Case and BPMN: Default entry point on the canvas
In BPMN, you can now right-click a start event and select Set as default entry point. In Case, you can do the same on a trigger. Runs and deployments that don't specify an entry point start from it, and nothing changes until you set one.
Debugging in Studio Web also starts from it: the Debug configuration dialog preselects it, and a start event you pick in the dialog is still remembered. The default start event's marker now sits inside the start event, at the bottom left.
For more information, refer to the following pages:
BPMN: End event outputs as arguments
In BPMN, the outputs of a message or connector end event, such as its response, now appear under Arguments in the Properties panel. The process returns them, and you can rename them.
Connector requests fail on vendor errors
Integration Service connector activities and HTTP requests now fail when the vendor system answers with an error status, meaning anything other than 2xx. Previously, the request showed as successful, and the vendor's status was only in the response body.
The error has the code IntSvcVendorRequestFailed (102021) and the message Received failure from vendor system on API - <url>: HTTP Status: <code> - <vendor message>. Error handling and retries follow the vendor's status: a 4xx stops, and other statuses are retried. On a send task, a vendor 5xx is reported as 502.
For more information, refer to Error handling.
Case: New Case app API endpoints
The Case app v3 API has two new endpoints:
GET v3/caseapp/instances/{instanceId}returns a single case instance, with the same fields as the v3 list, including priority, priority reason, and throttling state. It requires theCases.Viewpermission.GET v3/caseapp/instances/{instanceId}/case-statusreturns the case's full current status: the case status and SLA, the current run of each stage and task, failed task runs, open stage selections, and open incidents. It requires theCases.ViewSummarypermission, instead of an Orchestrator folder permission.
For more information, refer to CaseApp requests.
Improvements
- The Help option for connector events is now available on Case tasks, as it is on BPMN nodes.
- Outputs in the Properties panel show a Renamed or Reassigned tag next to their name.
- You can reset a renamed file output, such as a connector's downloaded file, from the x on its chip.
- The Maestro designers in Studio Web recalculate styles about twice as fast.
Accessibility improvements
- You can click a spot on the canvas minimap to move the view there, or use the minimap with the keyboard: press Tab to reach it, pan with the arrow keys, and zoom with + and -.
- Screen readers can navigate the Case app by headings.
- The Add variable dialog, the variable picker, the C# expression editor and its Accept, Reject, and Insert variable controls, the expression test inputs, and the variable filtering checkboxes now have accessible names and better keyboard support.
- The subprocess View button, the task Replace and Delete buttons, and the Case validation error tooltip are announced by name.
- The keyboard focus indicator is back on the Events, Rules, and Agent rows of the Case manager properties panel, and working stage toggle switches are no longer announced as unavailable.
- Menu buttons and multi-instance markers now announce whether they're expanded or pressed. The case manager agent toggle, the escalation trigger options, and the Add new variable link have accessible names.
- Task info and stage column titles are announced as headings, and the Case app overview is announced as a list.
- Info card text and dialog edges have higher contrast in dark themes.
Bug fixes
Flow
- Running a single node inside a loop in debug no longer fails with
Cannot read property 'item' of undefined. - A type mismatch on the document input of a Validate extraction or Validate classification node is now a warning instead of an error, so it no longer blocks debugging or publishing.
Case and BPMN
- Debugging or publishing a Case or BPMN project that was never opened now completes its missing or outdated project files first, instead of failing with an unclear error.
- After you duplicate or rename a solution, BPMN task inputs and outputs are kept, without "A variable is unresolved" errors or a false "Arguments have been updated" message.
- Start event arguments are no longer lost or mixed up with trigger outputs, and custom outputs are kept when you change a task's activity or resource. If one of your outputs has the same name as an output of the new activity, you're asked before it's deleted. Clearing an activity now also removes its output variables.
- Switching an Integration Service activity in the Properties panel, for example from Get Record to Delete Record, no longer keeps the previous activity's settings.
- Selecting a connector task after you reopen a process or case no longer changes the file, and reopening a BPMN file no longer reorders a connector task's inputs.
- The Add element panel no longer flickers when you hover over a search result.
- BPMN evaluations are kept when you export and import a solution, and evaluation runs now start in Studio Web local workspaces.
Case
- Disabling the case manager agent now stops it from running. Its configured tasks are kept and come back when you turn the agent on again.
- Pausing a case that has an SLA now completes, instead of staying in Pausing until the SLA timer fires.
- Global event variables show the event name in the variables list, and global event filters offer only the variables available when the event is configured.
- Rules that use Wait for connector can use only case start variables, which matches what's available at runtime.
- Filtering the Rules table by a stage also shows rules whose condition references that stage.
- Case manager tasks, such as its agent, show the case icon in the execution trail.
- Duplicated cases in the same solution get their own case ID and role IDs when published.
VS Code extension
- Renaming a project is refused, and nothing changes, when
project.uiprojcan't be read. Previously, the file was overwritten and lost its stored details. - Packing or deploying a project now regenerates its resource bindings first, so resources removed from a flow stay removed.
- The debug toolbar no longer offers Stop for a run that already failed.
- Download as screenshot no longer fails when the diagram contains connector icons.
- The action picker no longer opens over a closed Properties panel, and popovers no longer appear behind the canvas.
- Open app task in debug runs correctly detects whether Action Center is available.
- The Case video guide shows a link to watch it in the browser instead of a player error.
- Variable chips have the right color in the Future dark theme.
November 10, 2026
Chat agents on the Flow canvas are generally available
Chat agents on the Flow canvas in Maestro Orchestrate are now generally available, after their Preview release in September 2026. Chat nodes combine to model real-time conversations, with capabilities such as:
- Routing based on what the user asks.
- Hand-off from one agent to another that specializes in the request.
- Fixed messages that don't use a large language model (LLM).
- Parallel branches that run while the conversation continues.
Once published, the chat agent reaches users on the chat channels that you choose, with usage metrics, execution traces, and user feedback. Voice agents remain in Preview.
For more information, refer to Conversational tools.
- November 13, 2026
- Case and BPMN: New connector configuration experience
- November 11, 2026
- Case: Case app (Modern) (Preview)
- Flow: Match all cases on the Switch node
- Case and BPMN: Default entry point on the canvas
- BPMN: End event outputs as arguments
- Connector requests fail on vendor errors
- Case: New Case app API endpoints
- Improvements
- Accessibility improvements
- Bug fixes
- November 10, 2026
- Chat agents on the Flow canvas are generally available