# July 2026

> July 2026 release notes for Studio Web in Automation Cloud Dedicated and Test Cloud Dedicated.

## July 23, 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. 

### 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.

### Jobs tab in the deployment details panel

The deployment details panel now includes a **Jobs** tab, showing jobs associated with the selected deployment. Selecting a job opens the Job Details sidepanel. The **Explore all** link opens the jobs page in Orchestrator.

For more information, see [Managing deployments](https://docs.uipath.com/studio-web/automation-cloud/latest/user-guide/managing-deployments).

### Updated project types and interface

Studio Web introduces updated icons, project-type names, and navigation improvements across the **New project** dropdown, the **Start building** modal, and the **Add project to solution** context menu:

- **New icons** — All project types use updated Apollo line-style icons. The new icons appear in project tiles, breadcrumbs, the project explorer, and import and add-project dialogs.
- **Renamed project types** — Three project types have new names: Agentic process is now **Maestro BPMN** (Business Process Model and Notation), API Automation is now **API function**, and Automations is now **RPA workflow**. Tooltips are also added for Flow, Case, Function, and Connector project types.
- **Redesigned solution tile** — Solution tiles display a deck of up to three project-type cards. Hovering over a solution tile cycles through the project types it contains.
- **Plus icon on the New button** — The **New** button always shows a plus (+) icon regardless of context.
- **Categorized project creation** — A grouped view of project types is available in the **New project** dropdown, the **Start building** modal, and the **Add project to solution** context menu. Projects are organized into three categories:

  - **Business orchestration**: Maestro Flow, Maestro BPMN, Maestro Case
  - **Task automation**: RPA workflow, Agent, API function
  - **Building blocks**: App, Function, Connector, Business rules, Escalation app

  This grouped view is not enabled by default.

### Duplication feedback

When you duplicate a project, Studio Web now shows a toast notification indicating that duplication is in progress. For more information, see [Managing projects](https://docs.uipath.com/studio-web/automation-cloud/latest/user-guide/managing-projects).

### RPA local run without debug breaks

You can now run an RPA workflow locally from Studio Web without the debugger pausing on handled exceptions — exceptions caught by **Retry Scope** or **Try Catch** activities. No publish step is required.

Running locally without debug breaks is equivalent to running from UiPath Assistant: handled exceptions are processed inline without interrupting the run. For more information, see [Running and publishing RPA workflow projects](https://docs.uipath.com/studio-web/automation-cloud/latest/user-guide/running-and-testing-rpa-workflow-projects).

### Resource mismatch hint at debug time

When a resource bound to an activity has a different definition available at debug time than at design time, Studio Web now displays a warning hint on the activity. The hint indicates that the debug run will use a different resource definition and includes a link to update the resource mapping directly.

### Bug fixes

* Fixed an issue where default values could not be entered for **Object** or **Array** variable types in the data manager.
* Fixed an issue in the **File Created trigger** where the SharePoint Document Libraries folder picker did not allow selection of folders outside the initial visible list. Items that required scrolling could not be selected.
* Fixed an issue where the **Default value** placeholder for **Out** and **In/Out** arguments displayed "Enter text" instead of indicating that default values are not supported for those argument directions.