UiPath Documentation
studio
latest
false
Studio release notes
  • Release notes
    • 2026
      • September 2026
      • August 2026
      • July 2026
      • June 2026
      • May 2026
      • April 2026
      • March 2026
      • February 2026
      • January 2026

September 2026

September 2026 release notes for Studio.

September 22, 2026

Build number: 2026.0.202

Start a solution from the start page

Creating a solution used to mean creating a process first, using a Create new solution checkbox inside the New Blank Process dialog. The Start page now has a Solution option that creates an empty solution directly — add projects to it afterwards. For details, refer to Creating solutions in Studio.

Resolve merge conflicts in text files

A conflict in a text file (a .cs coded workflow, a .json configuration file, a .txt file, and similar) used to leave you with raw conflict markers and a plain text editor. Text files now open in a three-way merge view instead, with Local and Remote panes plus an editable Result pane. A conflicted .xaml workflow still opens in the visual workflow diff. For details, refer to Solving Conflicts.

A What's new page for coding agents

Opening a project now shows a What's new page that introduces coding agents across the automation lifecycle and presents Autopilot as UiPath's own agent alongside whichever agent you already use. It links to the Tools page where the UiPath skills and the UiPath CLI are set up. The page appears once per content revision rather than on every project open, stays reachable afterward from Help or an empty designer, and leaves out its Autopilot content if governance has turned Autopilot off.

Improvements

  • The arguments dictionary that the Invoke Workflow File activity opens now has a search box. A matching entry can be selected while the filter is still applied, and clearing the filter brings that entry into view instead of returning the grid to its previous scroll position.
  • Invoke Workflow File validation no longer stops a build or debug session at the first problem it finds. All argument mismatches are now reported together, the kind and type mismatches of a single argument are reported as one entry, and an argument that differs only between In and In/Out is reported as a warning rather than an error. Compiler errors and warnings in the Errors panel can be selected to navigate to the activity that produced them, and invoke activities that have been commented out are no longer validated.
  • With the Compact Design Experience setting enabled, a container activity no longer displays the header of the Sequence that makes up its body.
  • The agent-ready timeout used when starting a remote debugging session is now configurable, for machines where signing in takes longer than the previous fixed wait allowed.
  • Installing the GitHub Actions extension now also installs the git extension that it depends on.
  • Opening a Markdown file no longer recommends installing an extension to handle it, since Studio previews .md files itself.

Bug fixes

  • Studio could stop responding while opening a medium or large project, with the progress message stuck on Adding dependencies..., because of a deadlock that occurred when the coded-workflow language service was re-registered.
  • A VB project that also contained .cs coded workflow files intermittently reported spurious C# parse errors, such as CS1525 and CS1002, against files that were valid.
  • In a project containing only coded workflows, the generated CodedWorkflow.cs reported errors for referencing a WorkflowRunnerService that had not been generated.
  • Ctrl + D and Ctrl + E moved the selection to a different activity instead of disabling or enabling the activity that was already selected.
  • Run in Picture-in-Picture silently ran the process in the main session instead of the isolated one for Windows - Legacy projects.
  • An error indicator in the expression editor could stay in front of the expression while you were typing, hiding the text being edited.

September 8, 2026

Build number: 2026.0.201

Create Maestro Flow projects in a solution

A solution can now include Maestro Flow projects alongside your automation projects, created without leaving Studio. The Add to Solution menu in the Explorer panel has a new Create Flow Project entry that scaffolds a flow project into the solution — the same way uip maestro flow init does from the command line.

The .flow canvas itself is provided by the UiPath Maestro extension, which Studio recommends installing the first time you open a flow file. For more information, refer to Solutions.

Improvements

  • Workflow Compiler compile failures now carry the full underlying exception, including inner exceptions and stack trace, as expandable details on the error entry in the Output panel. The error line itself still shows just the message.

Bug fixes

  • The remote debugging target for an unattended robot — machine, folder, and robot — had to be configured again every time a project was opened, and a target configured in Studio was invisible to the uip CLI. The connection is now remembered per tenant and folder and shared between the two.
  • All case values of a Switch activity were silently cleared after a debug error followed by a rerun.
  • Converting a project from Legacy to Windows could silently resolve dependencies below the version the project requires, producing NU1605 downgrade build errors that Repair Dependencies did not fix.
  • The bundled .NET 8 runtime was updated to 8.0.30 to address reported security vulnerabilities, including CVE-2026-50650.

Was this page helpful?

Connect

Need help? Support

Want to learn? UiPath Academy

Have questions? UiPath Forum

Stay updated