Unanswered

PAD UI elements are hanging/failing

(2) Share

Report

Posted on by IA-29031218-0

I have a set of flows that have been running for years without issue - over the last few days they have suddenly started failing.

The problem is certian UI elements on the browser just hang. I need to use UI elements as with Microsoft Business Central its impossible to get reliable browser elements.

I have tested the selectors - they are absolutely fine - its just in run time they are hanging.

I have never seen a UI element hang before - if there is an issue they usually just fail.

Something has happened to PAD over the last few days - as I normally have a 99% success rate on completed flows - now they are failing 100%.

Do we know whats changed?

I have tried edge/chrome - i have done the usual - make sure browswer is up to date, PAD uninstalled/reinstalled / browswer extension remove and readd - everything.

Something has gone seriously wrong here with an update I would say. I will stress again - these have been running for years without issue.

Categories:

Power Automate Desktop

I have the same question (11)

All responses (7)

Answers (0)

IA-29031218-0 31 on at

Like (0)

Report

I have managed to roll back to the July version of PAD on one of my machines - and the issues are completely gone. Looking at the history of the release notes - the update on September the 5th contains fixes for 'adjustments around CUA functionality'

This has got to be what has broken my flows - MS please respond that you are fixing this!!!!

Even though I rolled back - I cannot connect it to the cloud as the installer to update the machine settings updates to the latest version of PAD - so im completely stuck!!!!

3 people found this reply helpful.

Was this reply helpful? Yes No
IA-29031218-0 31 on at

Like (0)

Report

Bump - this needs looking at by MS

Was this reply helpful? Yes No
Suggested answer

AH-10091557-0 3 on at

Like (0)

Report

A solution might have been one found in the Blue Prism community.

I don't use PAD, but saw this thread when searching for proof that this was a Chrome 140 issue which affected all UIA elements, and not just Blue Prism.

If the chrome/edge version has been updated to 140, the fault may lie there.

The solution is to append a command line argument to the launching of the browser, to disable the new UIAutomation renderer that Chromium forced as the default:

--disable-features=UiaProvider

I don't know if PAD has command arguments for browser or how you even launch, but this has saved the BP community from rolling back browser. Even then some elements may need re-work. Otherwise roll back your browser to version 139 if you can, and that might solve it better for you.

2 people found this reply helpful.

Was this reply helpful? Yes No
IA-29031218-0 31 on at

Like (0)

Report

Thanks, unfortunately im not sure you can run launch browser with command arguments - either way this needs looking at urgently by MS

Was this reply helpful? Yes No
IA-29031218-0 31 on at

Like (3)

Report

So there is a huge 6 page forum thread about this issue on the Blue Prism forums - with lots of useful info and acknowledgement from Blue Prism themselves that this is a known problem with Chromium/Edge 140. This is clearly a wide issue - yet from Microsoft we hear nothing. No support, no acknowledgement - nothing.

Its a disgrace that MS have been silent. Im going to keep bumping this daily until MS gives us an update or at least ackowledges this as an issue.

Was this reply helpful? Yes No
IA-29031218-0 31 on at

Like (2)

Report

Going to keep bumping this until MS aknowledges this as an issue

Was this reply helpful? Yes No
IA-29031218-0 31 on at

Like (0)

Report

Bump....

Was this reply helpful? Yes No