PowerAutomate Desktop - Clicking element in new Window

[jonathancavey]

Hello, 

I am new to PowerAutomate desktop and had the first part of an automated process built out and running three days ago.
The process I created that would open a browser (Firefox), go to a URL, click on a element to begin a download, then I would choose where I wanted to save it, rename it, save it, then open the file on the desktop. 

I had this all running smoothly and tested many times, but after the weekend the process will now no longer run. I keep encountering a error when, the browser (Firefox) opens a new Window asking what to do with the file, the flow will not click a button on the window(which it use to). I am using a 'Focus Window' and then a 'click UI Element' which are both succeeding during testing, but producing no results. 

I have tried recreating it a few times, and on different browsers and I keep encountering similar issues. 

Any help or other information regarding how to accomplish this another way would be greatly appreciated! 

Thanks

[Anonymous]

Hi @jonathancavey 

In picture #1, OK button appears disabled. I think that's why clicking on it doesn't work...

Are you sure the problem is related to PAD? Read, for example, this link: OK button on download window is disabled | Firefox Support Forum | Mozilla Support

[jonathancavey]

Yes, in that picture it is. 
When the process runs and it focuses on the Window it is not disabled (it will be disabled then will be enabled then you can see the clicking action happen). 
It also appears when it runs and it tries to click the 'OK', it scrolls the page down and the process is over. 


I will read that article now. Thanks!

[Anonymous · Accepted solution]

If it's all OK with Firefox and the problem is PAD, you can try a workaround sending key Enter to hit OK button:

'Focus windows' (focus your browser's window)

'Send keys' Enter ({Return}). Maybe it's necessary to send some Tab's before to get to OK button

[jonathancavey]

This is great - Thank you. 

While the enter does do the trick - can you think of any reason why clicking the button would cause the screen to scroll down and not click the ok? Just for my own curiosity. 

Thanks again for the quick reply and help 🙂 

[Anonymous]

No idea really! 🤔

[MichaelAnnis]

Double check your offset settings on that click.  What I have noticed is, when using the recorder on an image based recording, it takes a rather large picture and then offsets to the area of the picture where my button is.  So, later on, if you replace the oversized picture with a more accurate picture, but fail to reset the offset, then the offset stays, and it no longer clicks where you want it to.  I had this happen to me, and it kept missing it's target.  I'm wondering if your OK button may be next to your scroll bar and it just so lined up, that it's clicking your scroll bar.

Good luck.