UiPath 2025 September Community Release

[loginerror (Maciej Kuźmicz)]

UiPath 2025 September Community Release

Studio

Git – bring changes to a new branch

Until now, Studio users have often been blocked when switching branches. Unlike Git clients, Studio doesn’t support stash. Additionally, projects sometimes became “dirty” simply by being opened in a new Studio version (Designer auto-updates), which forced a commit on main before switching branches.

To solve this, we’re introducing a “Bring changes to a new branch” action. If you’ve made edits (or Studio has marked the project as changed) and you try to switch branches, you’ll be able to move those pending changes to a newly created branch automatically.

Improvements to the design experience

When working in large workflows with deep nesting, the breadcrumb path in the Designer header could quickly become hard to read. With the new look and feel, breadcrumbs now collapse into a dropdown once they exceed the available space.

This means you can:

• Quickly expand the dropdown to see the full path whenever needed.
• Avoid overflowing or truncated breadcrumbs in complex workflows.

We’ve updated the visual style of annotations to align with the new design:

• when unpinned, annotations now feature rounded corners;
• on cross-platform projects, pinned annotations are part of the activity card.

Assistant

Enhanced error messaging

We’ve revamped our error messaging system to provide more informative and user-friendly content. The updated system now offers additional context with a slightly revised UI, making it easier for users to understand and address any issues that may arise. Community users will now have the ability to search for similar issues directly on the Forum with just one button click.

Process execution visibility

We’ve enhanced the visibility of executing processes by adding a visual animation. This improvement provides users with a clearer indication of which processes are currently running.

UI terminology alignment

We’ve renamed several elements within the Assistant to improve clarity and understanding. These changes ensure consistency with our Assistant Web offering, providing a more unified experience across our products.

UI Automation

Edge browser support in cross-platform projects

Test Suite clients have requested the ability to run their automation tests across Chrome, Edge, and Safari browsers. Previously, Chrome and Edge were supported on Windows projects, while cross-platform projects supported Chrome and Safari. However, there was no project type that enabled testing across all three browsers.

We’ve now added Edge browser support for cross-platform projects, allowing users to develop and maintain a single project for comprehensive cross-browser testing. This enhancement simplifies automation efforts and improves consistency across platforms.

New modern activity – Window Operation

The new modern activity Window Operation can be used to perform various operations on the specified window element.

This activity must be added inside a Use Application/Browser activity, and the window on which to perform the operation can be:

• Main application window or Input Element - Apply the operation to the window specified either by the parent Use Application/Browser activity or through the Input element property.
• Specific application window - Apply the operation to the indicated window.

Closest matches information in exception message

In classic UIAutomation activities, when a target UI element isn’t found, the exception message includes information about the closest matches. Previously, for modern activities, this information was only available in the output panel and logs.

Starting with UIAutomation version v25.10.14-preview, the closest matches are now also shown directly in the “Runtime execution error” window. This makes it easier for users to copy and share the details with developers for faster troubleshooting.

Sticky “Enable Native Text” option in selection helper

The Enable Native Text setting in the UI Automation Selection Helper is now persistent. Similar to the behavior of the Enable Computer Vision toolbar button, once a user enables this option, it remains active the next time Selection Helper is opened. This enhancement addresses client feedback by eliminating the need to manually re-enable the option for each UI element.

“UnblockInput” Property Added to Modern Click Activity

The classic Click activity includes an UnblockInput property that helps handle pop-ups or modal dialogs that block the main UI thread. This functionality was previously missing in the modern Click activity.

Starting with UIAutomation v25.10.14-preview, the Unblock input property is now available in the modern Click activity. It should be used when the click action triggers a modal dialog or any other blocking UI element, ensuring the automation flow can continue smoothly without interruption.

Activities

Productivity activities - preview releases (3 September 2025)

Productivity activities - preview releases (3 September 2025)

New preview versions of the productivity activities On 3 September 2025 we released three new previews for the following Productivity activity packages: UiPath.Microsoft Office 365.Activities UiPath.GSuite.Activities UiPath.Mail..Activities Please read below what’s new in each of them Microsoft Office 365 - 3.4.1-preview Improvements The classic group of activities was moved under the Studio Classic activities filter for consistency with our other activity packages. Don’t f…

Please tell us what you think

Which features excite you the most and are you going to try right away? We want to hear what you think! Please use the button below

[David_Hernandez2 (David Hernandez)]

Do you have any examples of the “Unblockinput” property at work? Sounds useful, but I’m not sure exactly what sort of popups it would handle.

[macky999 (渚 佐伯)]

After updating to 2025.0.175-cloud.21052(Community Edition), I can no longer launch a project containing Tesseract OCR activities via UiPath Assistant.

An error message like the one below appears, and the project suddenly crashes.

I can run the project from UiPath Studio, so I think this is a bug related to UiPath Assistant.(This may only be a problem in the Japanese version.)

I would appreciate it if you could fix it.

Best regards.

[Nithinkrishna]

@loginerror

“UnblockInput” Property Added to Modern Click Activity

The classic Click activity includes an UnblockInput property that helps handle pop-ups or modal dialogs that block the main UI thread. This functionality was previously missing in the modern Click activity.

Starting with UIAutomation v25.10.14-preview, the Unblock input property is now available in the modern Click activity. It should be used when the click action triggers a modal dialog or any other blocking UI element, ensuring the automation flow can continue smoothly without interruption.

I tried using this, but there’s a shortcoming.

It attempts to click the element, but the time it does, the popup has disappeared. As a result, the popup block is successfully removed, but the click action fails. We can use workarounds like verify to retry, but ideally, the expected behaviour is to unblock the popup and perform the click in a single action flow.

[Raluca_Laic]

hi @macky999 , does the project contain only Tesseract OCR activities and is that the full error message?

[macky999 (渚 佐伯)]

Thank you for the quick reply.

I will upload the nupkg file and the project data, so could you please check it?

test.1.0.0.nupkg (68.0 KB)

test.zip (47.7 KB)

This is a very simple project that converts an image stored in the “test” folder into text using Tesseract OCR and displays it in a message box.

This process runs fine in UiPath Studio, but crashes via UiPath Assistant.

Even when I changed the OCR language setting from “jpn” to “eng” and converted the English image into text, the same problem occurred.

By the way, removing Tesseract OCR, I can start it without any problems from UiPath Assistant, so there is no doubt that Tesseract OCR is the cause.

The full error message displayed on UiPath Assistant is as follows:

{“Code”:“Robot”,“Title”:“呼び出されたワークフロー ‘Main’ には検証エラーがあります。ワークフローを確認して、エラーを解決してください。”,“Detail”:“System.Exception: 呼び出されたワークフロー ‘Main’ には検証エラーがあります。ワークフローを確認して、エラーを解決してください。\r\n —> System.Activities.InvalidWorkflowException: ワークフロー ツリーの処理中に次のエラーが発生しました:\r\n’Main’: アクティビティ ‘1: Main’ のプライベートな実装で次の検証エラーが発生しました: このバージョンの Studio でこのアクティビティを使用するには、v2.0.1 以降の UiPath.CoreIPC パッケージをインストールしてください。詳細については、ドキュメントをご覧ください。\r\n at System.Activities.Hosting.WorkflowInstance.ValidateWorkflow(WorkflowInstanceExtensionManager extensionManager)\r\n at System.Activities.Hosting.WorkflowInstance.RegisterExtensionManager(WorkflowInstanceExtensionManager extensionManager)\r\n at System.Activities.WorkflowApplication.EnsureInitialized()\r\n at System.Activities.WorkflowApplication.Enqueue(InstanceOperation operation, Boolean push)\r\n at System.Activities.WorkflowApplication.SimpleOperationAsyncResult.Run(TimeSpan timeout)\r\n at System.Activities.WorkflowApplication.BeginRun(AsyncCallback callback, Object state)\r\n at UiPath.Executor.RobotRunner.RunWorkflow()\r\n — End of inner exception stack trace —\r\n at System.Activities.Hosting.WorkflowInstance.ValidateWorkflow(WorkflowInstanceExtensionManager extensionManager)\r\n at System.Activities.Hosting.WorkflowInstance.RegisterExtensionManager(WorkflowInstanceExtensionManager extensionManager)\r\n at System.Activities.WorkflowApplication.EnsureInitialized()\r\n at System.Activities.WorkflowApplication.Enqueue(InstanceOperation operation, Boolean push)\r\n at System.Activities.WorkflowApplication.SimpleOperationAsyncResult.Run(TimeSpan timeout)\r\n at System.Activities.WorkflowApplication.BeginRun(AsyncCallback callback, Object state)\r\n at UiPath.Executor.RobotRunner.RunWorkflow()”,“Category”:null,“Status”:null}

Indeed, installing UiPath.CoreIPC, I can launch it even from UiPath Assistant.

But, another problem arises that it deteriorates the accuracy of OCR.

So, it would be very helpful if you could fix this bug.

[Luiza_Surdu-Bob (Luiza Bob)]

Hi @David_Hernandez2 ,

I’m providing a few additional details and an example to clarify how the UnblockInput property of the Click activity works.

It is important to mention that this property is only applicable to Java applications and works as follows.

The Problem
In some cases, certain buttons may trigger blocking dialogs on the thread where the Click is performed. When using the Simulate input method to click such a button, depending on the implementation behind it, our extension might hang until a user manually closes the popup. If the Java extension does not respond within a configurable timeout (default is 60 seconds), the click is considered to have failed.

The Solution
By enabling UnblockInput (setting it to True), the click via Simulate is executed on a separate thread, and we no longer wait for a response. This results in the following behavior: If the dialog opened is blocking, the extension no longer hangs, and the click is marked as successfully executed.

Example
Here is an example on how the problem can be replicated using UIAutomation v25.10.13 with the modern Click activity when the Simulate method is used.

ClickWithUnblockInput-25.10.13.zip (424.7 KB)

When running this workflow we will get an error for the Click activity:

And here is the same workflow that uses UIAutomation v25.10.14-preview, with the new UnblockInput property set to True for the Click on the button that triggers the blocking dialog: Click ‘Show Plain JFileChooser’. This workflow will run successfully.

ClickWithUnblockInput-25.10.14-preview.zip (333.7 KB)

I am also attaching the Java application SwingSet2 used for this example.

SwingSet2_withJava8.zip (1.5 MB)

[Luiza_Surdu-Bob (Luiza Bob)]

Hi @Nithinkrishna , I’ve added more information about this property in the previous response. Can you please check if your test matches the applicable scenario described there? And is it possible to share your test workflow? Thanks.

[Raluca_Laic]

thank you, @macky999 , I’ve filed a bug for this issue with the DU team and reached out to them.

[Nithinkrishna]

@Luiza_Surdu-Bob

Hi @Nithinkrishna , I’ve added more information about this property in the previous response. Can you please check if your test matches the applicable scenario described there? And is it possible to share your test workflow? Thanks.

Kindly check the behaviour once here.

#uipath #featureupdate #uipath #agentic #automation #uiautomation...

The above mentioned flow works only because of adding a verification with retry if not that would fail.

The unblock input either removes the popup from the screen or click the element in the background without closing the popup in the first attempt. Only if we have verification with retry enabled it goes for second attempt to click and for further action.

[Ferdinand]

When will DocPath be available in Europe when creating Document Understanding projects?

Currently the base model for invoices is still 24.4.