PAD taking more time to execute from a Power Automate flow

(0) Share

Report

Posted on by santoGD

Hi All,

I have a simple PAD flow to download a document from a web application.

I need to call this PAD flow inside a Power Automate flow.I have created a manual trigger flow to test the functionality in which I am only running the desktop flow.

Unfortunately, the processing of PAD action is taking 2 min on an average from Power Automate.

Can some one help if I need to do anything to process it faster.

Thanks

Santo

Categories:

Power Automate Desktop

All responses (4)

Answers (1)

Sort by

CristinaValdes 65 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi,
When you activate a desktop flow through a cloud flow, the time to connect to the machine to run your desktop flow is around 2 minutes, this time is included in the desktop flow runtime. Probably, this extra time that you notice is for this reason.
santoGD 58 on at

Like
a
(0)

Report
Copy link

Link copied!

Thanks @CristinaValdes .So How I need to change the time settings
CristinaValdes 65 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi, I found this steps, I hope they help you:
Access the Power Automate portal:
Sign in to the Power Automate portal with your Microsoft account.
Select the "Machines" tab.
2. Select the desired machine:
In the list of machines, find the machine for which you want to change the connection timeout.
Click the machine name to open its details page.
3. Edit machine settings:
On the machine details page, scroll down to the "Settings" section.
Look for the "Connection timeout" option.
Enter the new timeout value in seconds. The default value is 30 seconds.
4. Save changes:
Click the "Save" button.
5. Restart the machine:
For the changes to take effect, the machine must be restarted.

If the connection timeout is too short, Power Automate may not be able to connect to the machine and the desktop flow will not run.
Verified answer

Agnius Bartninkas Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!
You cannot change it. This is the time that cloud flows take to connect to the desktop, as well as return the status after the desktop flow is done.

The settings that @CristinaValdes mentions above will only make your flows timeout, if they don't connect in time. It won't make them connect faster.

There's really nothing you can do to make the connection faster, other than:

Making sure that the environment you use is in a region that is the closest to you (don't use US regions if you are in the EU and vice versa);

Making sure your network connection is as fast as possible.

Other than that, we just have to accept that there is some lag involved in the communication between the cloud and the machine.