- Automation Cloud and Test Cloud
- Automation Cloud Dedicated and Test Cloud Dedicated
July 15, 2026
Maestro Case and Maestro Flow (Preview) now available in Studio Web
Two new project types for business orchestration are now available in Studio Web.
Maestro Case (available since June 12, 2026) introduces a Maestro Case plan designer for goal-driven, exception-heavy processes where the next step is determined at runtime. Use it to model stages, tasks, rules, and SLAs for long-running work such as insurance claims, dispute resolution, or loan underwriting. For more information, see the Maestro Case release notes and the Studio Web Maestro Case documentation.
Maestro Flow (available in Preview since July 7, 2026) is a visual node-based Maestro Flow canvas for building lightweight process orchestrations that connect APIs, AI agents, human approvals, and enterprise services on the Maestro runtime. For more information, see the Maestro Flow release notes and the Studio Web Flow documentation.
July 10, 2026
Remove unused packages
We added a Remove unused packages action to the right-click context menu for both projects and solutions. The action identifies dependencies that aren't referenced anywhere in the project or solution and removes them. Before removal, Studio Web takes a snapshot of the solution, so you can roll back the operation if needed.
Add a project when cloning an empty repository
When you clone an empty Git repository to start a new project, Studio Web now prompts you to add a project. Previously, cloning a repository with no valid project file left Studio Web unable to load.
Improvements to the resource mismatch hint
Studio Web refines the resource mismatch hint introduced in June, which warns you when a bound resource has a different definition available at debug time than at design time. The improvements make drift easier to notice and let you re-sync a resource definition at any time:
- Warning icon inside the field — When drift is detected, it now surfaces as a non-blocking warning icon inside the Process field, next to the link to update the resource mapping.
- Refresh always available — The Refresh action is now always available, so you can force a re-sync of the resource definition even when no drift is reported. Drift detection is not guaranteed in every case, so a manual refresh remains an option at any time.