@eetuRobo Thank you so much for your response! I did consider making those changes, but it seemed a bit excessive for just a warning, so I only updated the Lunch instance to edge and everything worked fine.
If I was forced to use Automation Browser I would have did what exactly mentioned.
One way would be to add exception handling. So in Launch new Internet Explorer add On Error that makes it continue to next action. Maybe put Timeout on webpage load: 15 (or whatever timeout you think is suitable).
On error:
Then check if the Warning window is open.
If it is then Press button ‘Yes’ and after that attach the internet to browser instance.
For me atleast the action goes to error since it hasn’t loaded the page yet or something so I added On error Retry policy to try again 3 times and that fixed the flow failing.
Problem with this is that it will still give the same warning popup when ever you navigate to a different page. So if you click any link it will give same pop up (at least for me).
So you would need to do a subflow that triggers on error when on every action that is after you have clicked a link on the browser. Then that subflow would always click ‘Yes’ on the warning message.
Like so:
Then the subflow would look like this:
Now that will slow the process down quite a bit. So I recommend either switching to chrome/edge/fire fox or downgrading back to a version of PAD that didn’t give this error.
@martinaKolafova Yes I have the latest browser add on. But I'm talking about internal automation browser, not Edge or Chrome which uses add on extension.
Yup, I'm having the same issue with PAD automation browser. Problem occurred after the latest update to 2.51.344 :-/
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.