- Automation Cloud and Test Cloud
- Automation Cloud Dedicated and Test Cloud Dedicated
November 2026
November 2026 release notes for Studio Web in Automation Cloud Dedicated and Test Cloud Dedicated.
November 10, 2026
Auto-login for local setup
Studio Web now reconnects to UiPath Assistant automatically when Assistant isn't connected, or is signed in to a different organization or user. This setting, called Auto-login, is on by default, and you can turn it off from the Manage access menu. For more information, refer to Local setup for RPA workflow and app projects.
Updated sections and labels in the create menus
The options for creating a new solution or project in the Create New dropdown, the Start building window, and the Add to solution menu are now grouped under new sections.
Maestro project type names are also shorter (for example, Maestro Flow is now Flow).
For more information, refer to Creating solutions.
Improvements
- Activity fields of all types now behave the same way: selecting Variables shows the variable as a read-only chip, and selecting Expression editor opens an inline expression editor. When you switch a field back to its original control, for example Autocomplete, its value is kept if it's still valid for that control, and cleared otherwise.
Bug fixes
- Starting a debug session immediately after a new organization was provisioned could make debugging hang indefinitely without creating a job, with a page reload as the only recovery. Debug now starts correctly in this scenario.
- Opening the three-dot actions menu of an activity on the canvas sometimes required two clicks. The menu now opens on the first click.
- In app projects, the File scope of the Issues panel showed No issues found even when the open page had errors. The panel now shows the issues of the page you're viewing.
- Importing a project that targets the .NET 6 or .NET 10 runtime now shows a message directing you to open it in Studio Desktop, instead of failing unexpectedly. Studio Web continues to open projects that target the .NET 8 runtime normally.
- Debugging an API workflow that was part of a local solution no longer fails after you add a new project to that solution.
- Opening a project that included a
.entitiesfolder could fail on the first load attempt in the designer. These projects now open and run correctly on the first attempt, without requiring a retry.
November 5, 2026
Folder feeds when publishing and deploying solutions
When you publish or deploy a solution, you can now select a Tenant or folder feed as the place the package goes. For details, refer to Publish a solution to a feed.
Restore protection when others are editing
The Restore button in the publish history panel is now disabled while another user is editing the solution, so restoring a previous version can't overwrite their work. Your own other tabs or windows don't disable it. For more information, refer to Publishing and deploying solutions.
Non-destructive local branch switching
Switching local branches in the Version control panel no longer discards your uncommitted changes. If a change conflicts with the target branch, a confirmation dialog asks whether to discard it before switching. While the switch is in progress, the panel is disabled and shows the name of the target branch. For more information, refer to Version control for solutions.
Paste key-value pairs into dictionary properties
You can now populate a dictionary property in API workflow activities, such as the Query parameters field in the HTTP request activity, by pasting multiple key-value pairs at once instead of adding each entry manually. You can also switch the Dictionary editor to a text view to edit all entries together.
Improvements
- Designer tabs for open files now show a dot marker next to the file name when the file has unsaved changes, so you can tell at a glance which files still need saving.
- Variable and argument types in the Data Manager for RPA workflow projects now display both the friendly name and the underlying data type, for example Number (Integer) or Number (Double). For more information, refer to Variable and argument types.
- When you can't publish or debug a solution because one or more of its projects aren't ready, the error notification now lists each blocking project and the reason it isn't ready, such as an activity package that can't be found. Previously, a generic error appeared without identifying the project. For more information, refer to FAQ.
- You can now press the Esc key to close the Expression editor without saving your changes, the same as selecting Cancel.
- Debug sessions now start faster in solutions that contain apps not used as action apps, because Studio Web no longer publishes these apps before debugging.
Bug fixes
- Starting a debug session could stall without an error message if Studio Web couldn't connect to a service it needs. Studio Web now stops the debug session and displays an error message within about a minute, so you can try again.
- A failed solution overwrite, for example during debugging or publishing, could leave the solution unreadable: opening or exporting it returned an error, even though the solution still showed as available. Studio Web now keeps the solution's content when an overwrite fails, and shows an error status if the solution can't be restored.
- Valid JavaScript expressions in API workflows could show false validation warnings or errors, for example in workflows generated by an agent or the UiPath CLI. These expressions now validate correctly.
- Publishing a solution that included a Maestro Flow project could fail during package installation because the packaged project contained an invalid entry point identifier. Studio Web now corrects the identifier automatically before installation.
- Saving an app project before its required dependencies were installed could show a misleading Cannot save: workflow containing activities incompatible with Studio Web message, even though the page was saved. Studio Web now explains that saving is paused until the dependencies are installed.
- After you switched tenants, the designer could keep using data or components from the previous tenant. Studio Web now reloads the page when you switch tenants, so the designer uses the newly selected tenant.
- Publishing a solution set to run on your local machine could hang indefinitely. Publishing now runs on the selected machine, and if that machine has no available session, it fails within seconds with an error message that identifies the machine.
- Opening a local solution connected to a Git repository could rewrite parts of a workflow file even when you hadn't made any changes, creating unnecessary version-control differences. Workflow files are no longer modified unless their content actually changes.
- Opening and saving a workflow generated by Autopilot reformatted the entire file because Autopilot-generated workflows did not use the same formatting as the Studio Web designer.
- Publishing an API workflow created before a required configuration file was introduced could fail with a "Corrupted solution package" error. Opening the project now regenerates the missing file automatically.
- Bullet and numbered lists in rich text fields, such as the Rich Text Editor, did not render their markers as expected. The list text saved correctly but displayed as a plain paragraph.
- November 10, 2026
- Auto-login for local setup
- Updated sections and labels in the create menus
- Improvements
- Bug fixes
- November 5, 2026
- Folder feeds when publishing and deploying solutions
- Restore protection when others are editing
- Non-destructive local branch switching
- Paste key-value pairs into dictionary properties
- Improvements
- Bug fixes