UiPath Documentation
studio-web
latest
false
  • Automation Cloud and Test Cloud
  • Automation Cloud Dedicated and Test Cloud Dedicated
      • June 2026
      • May 2026
      • April 2026
      • March 2026
      • February 2026

Studio Web release notes

June 2026

June 22, 2026

View linked Automation Hub ideas

You can now view the Automation Hub idea linked to your solution directly from the Solution Properties panel in Studio Web and navigate to the idea profile from there. For more information, see Linked Automation Hub idea.

Save cloud projects to your Local Workspace

You can now save individual cloud projects directly to your Local Workspace. For instructions, see Saving a cloud project to your Local Workspace.

Expandable items in the publish history panel

Version items in the publish history panel are now expandable for solution projects. For more information, see Publishing and deploying solutions.

Log Message activity in API Workflows

Studio Web now includes a native Log Message activity in the API Workflow designer. Previously, logging in API Workflows required writing custom JavaScript code. The Log Message activity provides a low-code alternative for recording diagnostic messages, consistent with other native activities such as Assign and Try/Catch. For more information, see Log Message.

Test-case files in Studio Web now display a direct link to the associated test case in Test Manager. Previously, navigating to a linked test case required manual navigation to Test Manager. For more information, see Managing and running tests.

Default branch name is now main

When you initialize a new repository in Studio Web using the Initialize repository button, the default branch is now named main instead of master. This applies only to new repositories initialized through Studio Web. Existing repositories are not affected and keep their current default branch name. You can rename any branch manually at any time.

New deployment experience for solutions in Studio Web

You can now deploy solutions directly from Studio Web without leaving the application. The Publish button in the Build toolbar now includes a Deploy option that opens a guided deployment panel. The panel covers the full flow — packaging, configuration, and activation — in one place, with a live steps view and log output as the deployment runs.

A similar deployment experience is now redesigned and integrated in Solutions and Orchestrator. For more information on the Solutions updates, refer to the June 2026 release notes in the Solutions Management documentation.

For more information on the new experience in Studio Web, see Publishing and deploying solutions and Managing deployments.

Other new features

  • Studio Web now displays specific error messages when serverless execution fails, covering scenarios such as credits exhausted, concurrency limits reached, execution timeouts, and scheduling failures.
  • In projects with multiple agents, the tabs in the developer pane now display the agent name instead of Definition, making it easier to identify which tab corresponds to which agent.
  • Three new options are now available in the Explorer panel right-click menu for managing projects in a local workspace solution: Add existing project, Exclude project, and Reveal folder.

Improvements

  • Project names in the Add project to solution modal are no longer truncated. The layout now allocates more space to the project list.
  • You can now debug a solution even when a project within it is opened in read-only mode. Previously, the Debug button was unavailable for projects that were locked.

Bug fixes

  • Editing any property on an Integration Service connector activity in an API workflow that was saved before the property caching feature was introduced caused an Updating property failed error. This is now fixed.
  • Fixed an issue where selecting Publish in the Local Workspace produced no visible response. The publish operation now works correctly, and the next available version number is calculated automatically.
  • Fixed an issue where updating a solution template caused all dependencies (except uipath.system.activities) to be dropped when creating a new solution from that template.
  • Fixed an issue where Apps activities became unusable after adding an RPA (Windows) project to a mixed Studio Web and Studio Desktop solution. The metadata that links workflows to Apps controls is now preserved correctly.

Was this page helpful?

Connect

Need help? Support

Want to learn? UiPath Academy

Have questions? UiPath Forum

Stay updated