Release 2.27.177.22340 has broken my web automations

(3) Share

Report

Posted on by Cobyc

With the release of 2.27 and the new updated Edge extension, my automations are not working any more.

My Developer tools are enabled as per the requirements.

The web page I'm interacting with uses a lot of javascript to navigate to and from pages , it's 3rd party so I don't have any access to code.

Running any sort of javascript before calling a standard function like 'Press button on web page' will highlight the button but then the flow hangs and in the console of the developer tools I get a message

'Refused to run the JavaScript URL because it violates the following Content Security Policy directive: "script-src 'self' 'wasm-unsafe-eval'". Either the 'unsafe-inline' keyword, a hash ('sha256-...'), or a nonce ('nonce-...') is required to enable inline execution. Note that hashes do not apply to event handlers, style attributes and javascript&colon; navigations unless the 'unsafe-hashes' keyword is present'

This then also blocks the website from taking any user input, manual or automated.

I can't even roll back because you can't download version 2.26 anywhere and when I tried an older one I did download 2.23, I get a message that the flow can't be opened in the old version because it was edited in a newer version.. great.. just great! so now none of my automations work!!

EDIT:

I get that error even after removing the 'Run javaScript function on web page' methods, I also get it after using a 'Get details of element on web page' method.

This is ridiculous!!

Categories:

Power Automate Desktop

I have the same question (0)

All responses (21)

Answers (0)

Sort by

BalamuruganDev 57 on at

Like
a
(1)

Report
Copy link

Link copied!

Hello @Cobyc ,

Try to re install PAD and browser addons, restart machine, disable previous version browser addon if exist.

Thanks,
BD

Was this reply helpful? Yes No
Cobyc 21 on at

Like
a
(3)

Report
Copy link

Link copied!

@BalamuruganDev Thanks for the suggestion , but I have done all of that, I set up a small test for the specific web page and the behaviour was the same.

I managed to find an install of 2.26 on a different machine, so it is all working again.

Our company will probably look at a different automation tool as this kind of behaviour is causing too much disruption.

Was this reply helpful? Yes No
wnzn 168 on at

Like
a
(2)

Report
Copy link

Link copied!

I have had the same experience with multiple updates which were supposed to fix issues but just introduced others. At this point, it still has not run issue free since we started out a year ago. I think your company is taking the right decision as this tool is just not mature enough to be used in any serious scenario.

Was this reply helpful? Yes No
Dynamo 50 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi,
can you provide the 2.26 installation package? I'm having a similar issue.

Was this reply helpful? Yes No
maykolrypka 5 on at

Like
a
(0)

Report
Copy link

Link copied!

Hello! I'm having the same issue, could someone provide the URL to download an older version?

Was this reply helpful? Yes No
LeonCao 6 on at

Like
a
(1)

Report
Copy link

Link copied!

Hello, same issue, here. it's not only break the flow. it break the data. I think the browser add on defect will clear the table data some here. I need find a way to roll back to last version .

Was this reply helpful? Yes No
Miguelbernal 10 on at

Like
a
(4)

Report
Copy link

Link copied!

hi everybody

i know how it feel's had this kind of problem and get no answer, so here is link to the 2.26 version:
https://drive.google.com/file/d/1-2OrjOz7u2SOtFq57mcHKT1iGcdMWlPB/view?usp=share_link

if you are working with pad, make sure always have copy of older installers, for multiple issues with the new versions.
have a Nice day

Was this reply helpful? Yes No
MichaelNelson 12 on at

Like
a
(3)

Report
Copy link

Link copied!

I think we located the source of this issue. At least we ran into it ourselves. Before updating, we were using the Chrome Power Automate Desktop extension (Legacy). When we installed the most recent update, a new Power Automate Chrome extension was added instead, and PAD no longer work with the (Legacy) extension version.

The problem is, if we are trying to click a link that has an HREF of a javascript command, it won't work. So this sort of link will work:
<a href="https://www.google.com">Go To Google Directly</a>

But this sort of link will not.
<a href='javascript&colon;goToGoogle()' id="link">Go To Google via JS</a>

It USED to using the (Legacy) extension, but Chrome's "Manifest v3" stuff has forced that version into retirement. And this new version of the Chrome extension blocks javascript HREF references.

I think Power Automate Desktop needs to detect if has been blocked or, if possible, circumvent the restriction in the new extension. As it stands now, the "Click Link" command fails on these and the script hangs there forever.

As a sort-term solution, we have started replacing the link click with a javascript command to the browser. The command looks like this: document.querySelector("paste CSS selector here in these quotes").click()

Then we follow it with a "wait for element" to allow the page to load before the PAD code continues.

Was this reply helpful? Yes No
beebul 259 on at

Like
a
(0)

Report
Copy link

Link copied!

Yes I noticed this happens with those types of links too Michael, however unfortunately for me I can't modify the HTML as I am using a huge organisation web application that I can't modify.

I've had to roll back to an older version of PAD but I will do some tests with the legacy extensions.

Thanks for identifying the problem clearly and succinctly... Hopefully someone who can fix it will read this!

David

Was this reply helpful? Yes No
momlo 1,527 Super User 2024 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

@beebul You don't need to modify the page source; what Michael is saying is you can replace action in PAD with "run JS on the web page," where you call JS action to mimic clicking on the link/button/element.

This is very often faster in some scenarios than actions in PAD too

Was this reply helpful? Yes No