topic Re: Blue Prism UI Automation Failing after Chrome / Edge Update to 140 in Product Forum

Blue Prism UI Automation Failing after Chrome / Edge Update to 140

Adrian__Dones — Mon, 08 Sep 2025 16:29:31 GMT

Hi guys,

Hope all of you are well and have a great week start.

Starting from last week (around Wednesday~Thursday) Blue Prism fails while running to identify properly the fields spied using UI Automation mode.

While trying to check in Application Modeler if the fields can still be visible, they were successfully identified, but while running the whole process, somehow the process remains blocked while trying to access those fields.

The interesting part is that after re-spying the fields using UI-Automation (just to test if a new fresh set of fields would make the cut) the bot still fails.

Just to mention, the process worked properly without any errors more than 2 years and all of a sudden it failed to work anymore.

Please let me know if this is a general issue and/or how it can be fixed.

Much appreciated all your help 🙂

Re: [Blue Prism UI Automation Failing]

IACRA — Mon, 08 Sep 2025 08:48:58 GMT

Hi Adrian, we're having the same issues. A lot of our UIA elements are failing to identify while running, but are identifiable through the app modeller.

Best guess I've got at the minute is that there was an Edge update late last week. It seems the issue is prevalent across our company BP community, so definitely not an isolated case.

Re: [Blue Prism UI Automation Failing]

Adrian__Dones — Mon, 08 Sep 2025 09:01:26 GMT

Hi Iacra,

Many thanks for the fast response.

I'm using Chrome in the automations. I believe last week was an update also on it.

Do you have any idea if any workaround has been put in place?

Many thanks 🙂

Re: [Blue Prism UI Automation Failing]

IACRA — Mon, 08 Sep 2025 09:19:46 GMT

Nothing that I'm aware of sorry, I too was hoping to find some guidance here.

Re: [Blue Prism UI Automation Failing]

Adrian__Dones — Mon, 08 Sep 2025 09:22:23 GMT

Hi Iacra,

Found this:

https://support.blueprism.com/en/support/solutions/articles/7000095180-why-do-i-have-browser-automation-issues-after-updating-to-chrome-version-140-

Re: [Blue Prism UI Automation Failing]

Denis__Dennehy — Mon, 08 Sep 2025 09:53:58 GMT

My first thought is what has changed, because if nothing has changed your automation would still work. One of the most important things to get right when scaling an automation capability is managing change well (pre-change regression testing, monitoring while change is happening, having roll back plans if a change breaks stuff). In this case has Blue Prism changed, has the OS changed, has the application changed, has the environment speed changed? When you know what has changed getting to the root of why something has stopped working is far easier.

What controls are currently in place for OS updates or application changes (admittedly the later is problematic for SaaS apps on uncontrolled rolling updates). If it is the automation speed that has changed, then wait logic needs looking at.

You say that you had to respy everything to get your automation working again. Have you compared the previous element values to the new values. It might be that you need to make your element values more dynamic or deselect some to make your automation more robust to whatever has changed.

UIA element Issue

EricLi — Mon, 08 Sep 2025 10:20:00 GMT

we have blue prism upgraded from 6.10.4 to 7.4.1 a month ago. It is running well always, but today in certain application, most of the UIA elements do not work. As long as the first time operate on UIA element, it will be frozen to go forward. If I login the runtime resource and move mouse or type on keyboards, it will go on as usual. I reproduced on UAT, there is error message return as bellow:

Internal : Failed to perform step 1 in Navigate Stage 'SearchCriteria_UIA' on page 'SearchNo' - Exception during remote setforegroundwindow - System.ComponentModel.Win32Exception (0x80004005): Access is denied
at System.Diagnostics.ProcessManager.OpenProcess(Int32 processId, Int32 access, Boolean throwIfExited)
at System.Diagnostics.Process.GetProcessHandle(Int32 access, Boolean throwIfExited)
at System.Diagnostics.Process.OpenProcessHandle(Int32 access)
at System.Diagnostics.Process.get_Handle()
at BluePrism.ApplicationManager.Operations.WindowOperationsProvider.ForceForeground(IntPtr windowHandle)

Re: UIA element Issue

RoopkiranBevara — Mon, 08 Sep 2025 11:03:29 GMT

Hi @EricLi ,

we're facing the same issues. A lot of our UIA elements are failing to identify while running, but are identifiable through the app modeler.

Best guess there was an Edge update late last week. It seems the issue is with updating of browser. Lets wait for the solution from community.

Re: UIA element Issue

bclayton1896 — Mon, 08 Sep 2025 14:55:42 GMT

Alright, not going to blast 7.4.1, but we too have found issues after converting from 7.1.1 to 7.4.1.

We found specifically that there is a small visual difference between a newly created object's App Model, and an App Model for an object imported in from 7.1.1.

This observation was driven by a specific issue that arose when launchng an MS Edge app returning an error that "the process has detected another instance of Blue Prism that owns this session" and issues with the 7.4.1 browser extension not being detected - although the message broker host was running and available.

Recreating the object from scratch in 7.4.1 alleviated the issues above for us; this leaves us in a quandry as now we have a plethora of objects to recreate, across multiple applications.

One such issue we've run into is SAP. After the 7.4.1 upgrade, we noticed that some parameters for SAP screen elements no longer existed in our actions. We have not attempted to recreate the SAP objects yet, but we did some workarounds. These SAP objects were also imported from 7.1.1.

I don't know if this is good news, or bad news, but it is what we've discovered.

Re: UIA element Issue

david.l.morris — Mon, 08 Sep 2025 15:50:08 GMT

Just dropping these links here too. Known issue as of a few days ago. We are also having this issue in Edge Version 140.0.3485.54 in Blue Prism 6.10.1.

Why do I have Browser Automation issues after updating to Chrome or Edge browsers version 140? :

[BPE] BPNGRPA-10051 - Wait stages executed against Chrome and Edge 140 can cause Blue Prism Enterprise to pause/freeze and not proceed to subsequent stages :

Re: [Blue Prism UI Automation Failing]

david.l.morris — Mon, 08 Sep 2025 15:52:41 GMT

Same issue here Edge Version 140.0.3485.54 in Blue Prism 6.10.1. Blue Prism is aware and is investigating, as Adrian mentioned and linked to.

Re: [Blue Prism UI Automation Failing]

willem.borg — Mon, 08 Sep 2025 15:58:19 GMT

We're experiencing issues with UIA too. I really hope that there is an official solution from BP soon. For us it is affecting BP v6.10.5 and v7.3.1. Unfortunately we are not able to roll back to Edge v139.

Re: Blue Prism UI Automation Failing after Chrome / Edge Update to 140

Michael_S — Mon, 08 Sep 2025 16:31:29 GMT

Hey all, just wanted to drop in and say our engineers are investigating. I don't have any new information for you right now, and the best (and fastest) source of current information on this will be the Known Issue which @Adrian__Dones linked:

https://support.blueprism.com/en/support/solutions/articles/7000095180-why-do-i-have-browser-automation-issues-after-updating-to-chrome-version-140-

If the team have any questions, or I get any other info, I'll post it here.

EDIT: I have merged another post which discusses this issue into this one, just to keep everyone informed and the forum tidy 🙂

Re: Blue Prism UI Automation Failing after Chrome / Edge Update to 140

james.keefe — Mon, 08 Sep 2025 16:34:08 GMT

Same issue here, its caused some major havoc here. I can manually jig through stuck automations by wiggling the mouse/click/F5'ing hoping for the best but its not fun. The official answer of rolling back to earlier edge/chrome just isn't viable. 7.3.1 user

Re: Blue Prism UI Automation Failing after Chrome / Edge Update to 140

david.l.morris — Mon, 08 Sep 2025 19:50:43 GMT

As @james.keefe said, we're finding that we can get it to move forward by just moving the mouse around. In our case, we go into the Runtime Resource machine through vSphere and move the mouse around (sometimes have to click to get into the session so maybe the click is what does it sometimes), and then the stage becomes unstuck and moves forward. This seems to usually happens with wait stages (especially when an element is not found or when an element doesn't exist), but it also happens with navigate stages such as global mouse click.

I have been running tests all day in different scenarios for different automations, and I can't reliably reproduce the issue. I think a big reason for this is that the issue immediately goes away if you have clicked into the browser with a global click (whether manually or automatically). Because of this, you basically never see the issue in debug mode. I suspect it should actually be possible for it to happen in debug mode, but I haven't figure out how to make that happen yet.

Re: Blue Prism UI Automation Failing after Chrome / Edge Update to 140

stepher — Mon, 08 Sep 2025 21:52:14 GMT

Ours situation seems to be a mixed bag. Some automations ran successfully, and then the same Process on the same machine would lock up. In those instances, my Operations team were able to access the Runtime (via Bomgar) and it seemed to correct itself.

That said, once I had identified a specific action in an Object, my results were slightly different. If I stepped "into" the action and let it run, it was fine. If I stepped "over" the action, from the Process, it would lock up. That part squares with what @david.l.morris said. However, in this (many) instance, no amount of mouse activity got it to unstick. My only 'resolution' was to close out the browser (MS Edge, in my case) and that allowed the Action/Object to wake up (and throw an exception).

Looks like we are rolling back to v139.x. Should be fun.

Thanks,

Red

Version 7.4.1 has issues when working with Microsoft Edge Build 140.

sy_lee — Tue, 09 Sep 2025 05:17:41 GMT

Hello.

I've been trying various methods over the past few days to fix an issue where Blue Prism 7.4.1 isn't working correctly with Microsoft Edge Build 140.

First, I want to let you know that I was unsuccessful in downgrading Edge.

During my work, I found that when I use the Highlight function in Application Modeller, it correctly identifies the element. However, when I run tests using Step Over, a "More than one..." message appears, and the test fails.

This error doesn't happen on every website, but I believe it's helpful information to share.

I confirmed that the process works correctly when I set the Match Index value for elements that don't have one specified.

Although this hasn't been verified for a wide range of cases, so it may not be a complete solution, it could be a way to handle the current problem.

I hope this helps with the issue you're facing.

Re: Version 7.4.1 has issues when working with Microsoft Edge Build 140.

Ninoseki — Tue, 09 Sep 2025 05:37:06 GMT

Hello @sy_lee,

Thank you for sharing the information.

While reviewing the Chromium issue list—the core of many web browsers—I came across an interesting bug report related to UIAutomation. It appears to align with some of the details you provided, which makes this finding particularly relevant.
From Chrome 140+, multiple popup dialogs (e.g., Extension etc.) are detected via UI Automation tool [439716356] - Chromium

I hope this bug will be addressed and fixed in the near future, as it could have a meaningful impact on our work.

Best regards,
Yusuke Ninoeki

Re: Version 7.4.1 has issues when working with Microsoft Edge Build 140.

sy_lee — Tue, 09 Sep 2025 07:00:39 GMT

It seems this symptom is primarily found when UIA uses the *'Item' property.

Re: Version 7.4.1 has issues when working with Microsoft Edge Build 140.

Anton__Hosang — Tue, 09 Sep 2025 07:48:04 GMT

did you mean using the Wildcard attribute type?