Simple flow with Click UI element takes 30+ seconds before starting

[Aaron105]

I created a simple Click UI Element flow that pushes the buttons on the windows calculator.  From the time I press "run" until the first button is pushed is always 36-37 seconds.  Why am I getting a delay when I run my flows that click UI elements?

This is occurring in another flow using a different application, but still using the click UI element.  This is NOT occurring when I create a basic flow to read data from an excel workbook and store it in an Array.

Thanks

Aaron

[Nick_Nikol]

Hello Aaron!

It might be possible that the window is not properly focused before then. I'd recommend using a focus window action before? The flow may also be trying to grab the content before it's fully loaded which causes it to stall?

There is also an example flow under Desktop Automation that shows off the calculator being used so you can also use it for reference!

Let me know if this helped!

[Aaron105]

Hi Nick,

Thanks for the reply.  Adding the focus window action to my flow didn't help.  While running in debug mode, I can see it sitting at the focus window action for 37 seconds before moving to the Click UI Element.

I did try the calculator example you suggested.  After pressing Run, it takes 5 seconds for the calculator app to appear on the screen.  The flow then waits until 40 seconds before actions start occurring.  The action move at regular speed.

It seems that there is something that is causing a 35-40 second delay or lag when I use a flow that includes the Click UI element.  The real problem is it makes debugging miserable, testing a bunch of little changes takes way longer than it should.

Thanks

Aaron

[Anonymous]

i am doing a recorded flow, i am just trying to open the calculator and it takes 30 seconds. I have also set the time for delay down to 1 millisecond. same for command prompt. any suggestions or is this normal?

[Pavel_NaNoi]

Can't seem to re-create the issue for the calculator specifically, works perfectly fine for me,

HoweverI have found somewhat of a work around, as I've had this issue appear in Word.

Instead of using "Click UI Element in window" use "Get details of UI Element in window" then get the "Location and size", take this variable, use "Split Text" on it and split by space, now use a "Convert Text to Number" action on the 0'th and 1'st value of that list, those are the X and Y coordinates of where the UI Selector is, now just use "Send mouse click" and tell it to move mouse, and put the X and Y coordinates you've just created as to where it should move to, that should do it.

While this sounds a little bit hectic it works quite fast, I recommend putting the whole *split text - to send mouse click* actions into a subflow and just using it like that.