How can I speed-up the desktop flows execution

[pcand1001]

Hello,

When I start a desktop flow, I get the flow started notification.
This flow is sending the left window key, then type a string, then hit enter, wait for a window, type some text and start doing other things.
I have to wait 7 seconds for the first action to execute, then 5 seconds for the second action, then 7 seconds etc.
If I execute these steps by hand, I can do it much faster than the flow.
How Can I speed-up the execution?
See flow bellow.
Thanks,

Philippe

[miketran13]

Hi,

While debugging, you can change the delay time to speed up the execution. 

And when running without debugging, you have no worries about the speed.

Thanks and hope it can help you. 

Mike

---------------------------------

Did I answer your question? Please consider to Mark my post as a solution! to guide others

[pcand1001]

I was referring to the runtime from the console, not the debugging.
I guess that my question is still open. Now I think this PAF works by triggering something in the cloud.
Could that be why it takes so long to start the execution? network latency, firewall rules, filters, round trips etc.
Guys, I thought Automate Desktop was Desktop, not cloud. On Desktop their would be NO latency.
Thoughts?

[fraenK]

PAD always creates a flow session in the cloud environment before starting the flow to record the run details.

Are you using the latest version of PAD? https://powerusers.microsoft.com/t5/Power-Automate-Desktop/New-releases-Power-Automate-Desktop-clien...

Multiple seconds delay between actions sounds strange. Does the task manager show signs of high load? Or are there any other (security/display) tools running so PAD needs more time to catch the right window?

[pcand1001]

I have tested on work and home machine with an internet connection around 400/25Mbps. I do not see much load at the time I run these flows. I created a few flows, they are all slow, some are VERY slow. I installed the desktop version a couple days ago. V2.5.39.21056

[fraenK]

Latest version is 2.6.48.21069: https://download.microsoft.com/download/b/d/8/bd8409df-7b80-4ef7-89c5-5a7a941a5093/Setup.Microsoft.P...

[pcand1001]

I installed the version from the link, no change, still slower than what it should be.
I can do it manually in 9 seconds
Flow takes 35 seconds to complete
This was when using the window key and type the app name.
I changed to flow to use the Run Application action. This revised flow runs in 16 seconds, almost double than doing it manually. Still too slow.

[fraenK]

Maybe it's the application you're trying to automate?

Try to run and enter something in this AnyTellerDemo (just search for the name, had to remove the link, otherwise post was marked as spam and removed)

You can copy/paste the following code, just change the app path and add the selectors (3 fields + button):

DateTime.Local DateTimeFormat: DateTime.DateTimeFormat.DateAndTime CurrentDateTime=> CurrentDateTime
System.RunApplicationAndWaitToLoad ApplicationPath: $'''C:\\Users\\user\\Downloads\\AnyTellerDemo.exe''' WindowStyle: System.ProcessWindowStyle.Normal Timeout: 0 ProcessId=> AppProcessId WindowHandle=> WindowHandle
@@timestamp: '2021-03-19T17:53:14.8734109Z'
UIAutomation.FormFilling.PopulateTextField TextField: appmask['Window \'frmAnyTeller\'']['Edit \'WindowsForms10.EDIT.app.0.378734a\''] Text: '123'
@@timestamp: '2021-03-19T17:53:17.7583136Z'
UIAutomation.FormFilling.PopulateTextField TextField: appmask['Window \'frmAnyTeller\'']['Edit \'WindowsForms10.EDIT.app.0.378734a\' 2'] Text: '456'
@@timestamp: '2021-03-19T17:53:20.6835115Z'
UIAutomation.FormFilling.PopulateTextField TextField: appmask['Window \'frmAnyTeller\'']['Edit \'WindowsForms10.EDIT.app.0.378734a\' 3'] Text: '678'
@@timestamp: '2021-03-19T17:53:23.2672391Z'
UIAutomation.FormFilling.PressButton Button: appmask['Window \'frmAnyTeller\'']['Button \'Accept\'']
DateTime.Local DateTimeFormat: DateTime.DateTimeFormat.DateAndTime CurrentDateTime=> CurrentDateTime2
DateTime.Subtract FromDate: CurrentDateTime2 SubstractDate: CurrentDateTime TimeUnit: DateTime.DifferenceTimeUnit.Seconds TimeDifference=> TimeDifference
Display.ShowMessage Message: TimeDifference Icon: Display.Icon.None Buttons: Display.Buttons.OK DefaultButton: Display.DefaultButton.Button1 IsTopMost: False ButtonPressed=> ButtonPressed

Execution takes 3,9 seconds on my machine from the console

[pcand1001]

That is 9.4 seconds on my machine.
Teller opens quickly, then there is a few seconds delay before the first text is entered.

[fraenK]

Strange! Tried it on another machine and it runs in 4 seconds.

What CPU does your machine have?

[pcand1001]

I need to test from somewhere else than from my home network. I did run the same AnyTeller test on my home machine and it took 127 seconds!
The laptop is a XPS i7 10875H @ 2.3GHz SSD System 32GB RAM
The home machine is a Vostro i7 10700 @ 2.9GHz, SSD system 16GB RAM
Other test I could do, reboot Router, Disable anti-virus and firewall and see it that helps. Then Run the test on remote machine which is at work, then try on another older XPS laptop and work laptop as well on Wifi using my mobile phone as a hotspot?

[pcand1001]

I tried on a 3 years old machine at home and there the test runs in 5 seconds.

[fraenK]

So it must be a software issue, a common software on the other machines. Anti-virus/security or something from Dell, or driver or a multi-screen thing.

[pcand1001 · Accepted solution]

Unbelievable but I could resolve the issue by uninstalling the Win10 build-in Edge browser using command line and reinstalling it from the regular installer. Now AnnyTeller runs in 6 seconds.
I was suspicious of Edge on that new machine because it sometimes struggled to display a web page, showing an error for a few seconds before loading the page. Since some software will use components of Edge, I thought it might have been the culprit and it was. What is killing me is that this fix on my home machine causes PowerAutomate to work with the same performance on both my home machine and my work machine and I did not uninstall Edge form my work machine. I will do it anyway and test again. These machines are sharing the same screens and are connected to the same router.

[pcand1001]

please ignore