UiPath 2025 April Community Release
Studio
Studio UX refresh
We’ve made a number of visual tweaks to elevate the overall experience. These changes focus on improving clarity, consistency and the design experience.
Here’s what’s new:
- New color theme
- More compact layout for panels
- Command palette in the title bar
- Ribbon layout now compact by default
- Cleaner dialog boxes
- Larger modal widgets
- Redesigned scroll bars
Expand each section below if you’d like a before and after view of some of the changes.
Scroll bars
Detached Error Handler in Long Running Workflows
You can now use a Detached Error Handler to manage exceptions occurring within the Long Running Workflow. Unlike the Error Boundary Event, which is usually tied to a specific Task, the Detached Error Handler provides a global exception handling inside the canvas. This is because it is tied to an Exception and not a Task.
The Detached Error Handler is useful as it allows you to define more steps in the error handling process. For example, in an order fulfillment process, any failure during payment, inventory check, or shipment steps could trigger a Detached Error Handler that notifies the customer, updates the order status, and logs the issue for support.
This approach is ideal when you want robust and reusable error management across the entire process, rather than handling errors piecemeal at individual activities.
In the example below, I’ve added a Detached Error Handler to handle all possible exceptions occurring in the process:
When an error was triggered, execution was moved to the Detached Error Handler where I had a recovery using an Agentic Task:
You can add multiple Detached Error Handlers, as long as they handle different exceptions.
Error Boundary Event vs Detached Error Handler
| Error Boundary Event | Detached Error Handler |
|---|---|
| Use it when you want to catch an error for a single specific Task | Use it when you need to handle errors globally within the process |
| The error handling logic is simple and tied directly to one Task | You want to reuse the same error handling logic for multiple Tasks. The error handling is more complex and can involve multiple steps. |
| Example: An Error Boundary Event on a Send Invoice task catches a failure and routes the process to retry or notify the finance team and continue execution | Example: Any error thrown in a customer onboarding process triggers the Detached Error Handler that logs the error, sends an alert, and rolls back some changes. |
You can have both an Error Boundary Event and a Detached Error Handler on the canvas, handling the same exception:
-
if the exception is thrown on Task A, the execution will move on the Error Boundary Event path and go through Recovery Task A and Task B
-
if the exception is thrown on Task B, the execution will move towards the Detached Error Handler and recover it there
Performance improvements
Working with large projects? Studio’s now faster and more responsive where it matters most.
-
Workflow Designer: Up to 10x Faster Navigation
Large workflows scroll and render much faster now.
-
Manage Packages Search: From minutes to seconds
We drastically reduced search time when browsing “All Nodes” - this used to take minutes when having multiple feeds configured and searching for broad terms. -
Compile Expressions to Single Assembly
Reduces compile time by ~30%. A backend change you’ll feel in faster execution. -
Faster Locals Panel
Expanding JIT-compiled objects used to take up to 10 seconds — now it’s instant for most objects. In the next release, we’ll improve this further by adding full support for nullable types, so even those edge cases expand instantly.
Continuous improvements
-
Output Panel v2
Context-aware logs. Persistent compile output. Full-text search.
-
Auto-Scope for Modern Activities
For activities that require a parent container (or a scope), Studio will automatically add it on the canvas when it’s not present. -
Generate Variables from JSON Schemas
Paste a JSON schema and instantly create a strongly typed variable. It’s now easier to create, maintain, and work with structured data — especially when interacting with APIs, complex objects, or Agents.
This initial version supports first-level properties, with nested structures coming soon in a future update.
-
Default Zoom Settings
Studio now remembers your preferred zoom. Navigate Backstage and configure it in the Settings. -
Export to Excel has moved under the Export as button
Robot
Enhanced Workflow stack trace
Error logs now provide details about the activity that caused your workflow to fail, including the workflow file name, activity name, and container hierarchy. These details help you quickly locate the activity within your project, and are displayed in Studio, Orchestrator, and Robot logs.
Assistant
Action Center integrated as a tab in Assistant
Starting in version 25.4, the Action Center is now accessible via its own dedicated tab, replacing the previous separate window. This one-click tab switching is part of our effort to deliver a more unified and seamless user experience.
Reload
We’ve introduced a Reload button as a one-click solution to refresh the application, eliminating the need to Quit and Reopen or Log Out and Log In. It’s especially helpful in situations such as:
- When policy changes need to be applied - like enabling/disabling features or updating permissions for specific groups.
- When new widgets have been installed or if you’re encountering widget-related errors.
UI Automation
Dialog Handling App Card options and Project settings
Starting with UI Automation v25.2 we introduced the Browser Dialog Scope activity which can handle common JavaScript browser dialogs (alert, confirm, prompt), in Chrome or Edge, both in Windows and Cross-platform projects. The activity is not yet available for the Firefox browser.
From version 25.4 we complemented the Browser Dialog Scope functionality with browser dialog handling options added to the Use Application/Browser activity.
The new Dialog Handling options section in the App Card allows users to describe how to auto-dismiss browser dialogs (which types of dialogs to dismiss and what response to give to confirm and prompt dialogs).
- Dismiss Alerts
- Dismiss Confirms + Confirm dialog response
- Dismiss Prompts + Prompt response text + Prompt dialog response
We have also added similar project settings for Dialog Handling, which work as defaults for the Use Application/Browser Dialog Handling options.
- Windows projects: UI Automation Modern > Application/Browser
- Cross-platform projects: UI Automation > Application/Browser
AppSignatures package for Chromium Native signatures
Chromium Native signatures have now their standalone package (UiPath.AppSignatures) that can be used to update the signatures as quickly as possible for a given Driver, without having to change and retest the entire UI Automation package. The new package should be added as a Nuget dependency on our UiPath (Driver) package.
From version 25.4 the AppSignatures package is published together with the Driver package. Version 25.4 of the UiPath.AppSignatures package will be fully compatible with the UiPath.UIAutomation.Activities package v24.10.6 or higher.
For instructions on configuring package dependency and deploying to a remote machine, you can check the official docs page: AppSignatures package for Chromium Native signatures.
Modern Get/Set Clipboard activities available in UI Automation API
Customers working with coded workflows asked for an API for Get from Clipboard and Set to Clipboard activities.
To achieve this, UI Automation v25.4 introduces modern versions of classic activities: Get from Clipboard and Set to Clipboard, in Windows and Cross-platform projects.
Important mention for Cross-platform projects: modern Set Clipboard / Get Clipboard activities will only run on Windows or MacOS. Other operating systems are not supported.
The new modern activities can also be used in coded workflows.
Clipboard based copy-paste execution mode for Type Into activity
When using Hardware events to type with the Type Into activity, some applications don’t receive the text correctly. In these cases, a workaround could be used:
- Set to Clipboard the text you want to type.
- Send Hotkey of
Ctrl+V.
Sometimes, this workaround may also perform faster than the Type Into activity with delay between keys set to 0.
The Type Into activity now offers enhanced flexibility with a configurable clipboard usage strategy. This improvement ensures that text input is both efficient and adaptable, allowing automation to seamlessly handle various application behaviours.
We added a new property, Type by clipboard, which indicates whether the clipboard is used to type the given text. The following options are available:
- Never – Never use the clipboard.
- Always – Always use the clipboard.
- Whenever possible – Use the clipboard when possible. This depends on the OS and the text to be typed (e.g. if any special key is used, then the clipboard will not be used).
WaitForPageLoad property for Get URL activity
The WaitForPageLoad property is already available on most UI Automation activities. Starting with UI Automation v25.4 this property is also available for the Get URL activity, with the following possible values:
- None
- Interactive
- Complete
Window attach mode setting in Project settings
Use Application/Browser activity has the default value for the Window attach mode property equal to Application Instance, which means a Window selector exists in every UI Automation activity placed inside the App Card.
Many automations use different Window selectors for Dev, Test, and Prod target applications. Sometimes developers don’t pay attention to the Window attach mode property of Use Application/Browser. They do their whole project without realizing this and then must clean it up later.
With UIAutomation version 25.4 we introduced a project setting that allows users to default the Use Application/Browser’s Window attach mode property to Single Window. Users can now set it this way in their automation templates.
The new project setting in UI Automation Modern > Application/Browser section, has the following options available and will apply to newly added Use Application/Browser activities:
- Application instance – Inner activities will search in the indicated application instance, including all parent and child windows (alerts, popups, etc.). Other instances of the application are excluded.
- Single window – Inner activities will search only in the indicated window.
Please tell us what you think
Which features excite you the most and you are going to try right away? We want to hear what you think! Please use the 
button below 
Especially since I use keyboard shortcuts for my most used actions. If I don’t remember how the icon I need to click looks like I can easily expand labels with one click 
And I’m sure this is true for all seasoned users 