Answered

Performance and response time problem in Power Automate Desktop when executing action stream

(2) Share

Report

Posted on by BrandCastro

I have a problem with Power Automate Desktop. The flow I am building recorded actions, which I adjusted as needed, such as pauses and error handling. In one of these actions, “number”, the bot expects to open a window and click “OK”. This action should take 10 to 12 minutes to finish when done manually (Human).

However, when I run the “number” action from the bot, Power Automate Desktop opens the window smoothly, but does not respond for 10 to 15 minutes. It does not find the “OK” button, and when it does, it can take 1 to 2 hours to complete the action, causing the flow to fail.

In contrast, when a human performs the numbering action, it takes no more than 2 minutes to respond and click “OK”, completing the task in about 5 minutes.

What I have done so far:

Check resources: CPU varies between 17% and 89%, RAM (16 GB) is at 52%, and HDD is at 60%.
Change the window wait action to a counter and click on X and Y coordinates.
Exclude the antivirus from “C:\ProgramData\Microsoft\Power Automate”.
Validate the administrator permissions for PAD.
Validate the NT SERVICEUIFlowService.
Review group policies.

Categories:

Power Automate Desktop

I have the same question (0)

All responses (4)

Answers (1)

Sort by

eetuRobo 4,513 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

To clarify is "number" a subflow or a region which has multiple actions or what?
And does the flow get stuck only at the action where its trying to press "OK" button or is it stuck at "Wait for window" -action?
Have you tested the UI elements that are causing the flow issues? So the Window element and the Ok element.
Open the UI Elements view from the side bar:
And open the element that the flow gets stuck on and press "Test" (while the UI window is open where the "OK" button can be pressed). Also the the Window(parent) element.
It should give green check marks but if it give yellow icon or error then something is wrong and you need to fix the elements. If its yellow icon then the UI element is not specific enough and it finds competing elements.

Was this reply helpful? Yes No
BrandCastro 30 on at

Like (1)

Report
Copy link

Link copied!

It is a little strange, because if the flow clicks on numbering it takes N amount of time. If you do the test when it doesn't respond it comes up with an error of not finding window, if I wait for the window to respond it gives as OK wait.
I remind you that it only happens with this numbering window.No response

Wait a few minutes for the window to respond

Wait a few minutes for the window to respond

Was this reply helpful? Yes No
eetuRobo 4,513 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Do you have many of those "Actualizar Monedas" -windows open or just one? I recommend trying to toggle off the Class which you have value FNQNS3126 and seeing if that makes a difference. There is a possibility that it is dynamic and changes every run.

Also check also the actual Window (parent) element of those UI elements that are going to error or taking a long time to be found. Example pic of the parent window:
Test that and try to check if you could modify it to work better (don't take attributes that are dynamic but try to make it specific enough so the flow finds it quickly).

Was this reply helpful? Yes No
Verified answer

BrandCastro 30 on at

Like (1)

Report
Copy link

Link copied!
It was identified that the process of the app was getting blocked and taking much longer when Power Automate Desktop was running compared to when PAD was stopped.

Once this was identified, documentation was consulted, and the following related article was found and the proposed solution was applied:

Desktop application crashes in UI automation

In summary, to resolve the issue of blocking in Power Automate Desktop and the app when running simultaneously, two specific settings that affect UI automation were modified. These settings disable the monitoring of certain events that can cause conflicts and result in blocking.

Modified Parameters:

UIA3.DisableFocusEvent:

Function: Disables monitoring of focus changes of elements in the user interface.

Impact: Disabling this monitoring can prevent conflicts that arise when focus shifts between different windows or controls, which may help prevent the application from blocking.

Values:

true: Disables the focus change event.

false (default): Keeps the focus change event enabled.

UIA3.DisableWindowStateEvent:

Function: Disables monitoring of window state changes, such as minimizing, maximizing, or restoring.

Impact: Disabling this monitoring can prevent conflicts and blocking that occur when window states change in applications managed by Power Automate.

Values:

true: Disables the window state change event.

false (default): Keeps the window state change event enabled.

Was this reply helpful? Yes No