Power Platform Community Forum Thread Details

Hello,

I am facing an unexpected behavior in Power Automate Desktop and I would like to understand whether it could be related to a recent update.

I am using the “Wait for window” action with a timeout configured to 20 seconds. In addition, my desktop flow has a global timeout configured to 5 minutes.

However, despite this configuration, the action does not stop after 20 seconds as expected. Instead, the selector is detected only after approximately 30 minutes, and the action eventually completes successfully after this long delay.

During this entire period, the execution remains blocked, which is particularly problematic because while the desktop flow is running, it prevents other flows in the queue from starting.

I do not understand why:

- the action timeout (20 seconds) is not respected,
- and the global desktop flow timeout (5 minutes) is also exceeded

The final behavior is therefore inconsistent with the configured timeout, even though the action ends successfully after a long wait.

I started noticing this behavior around April month, whereas it did not occur before, which suggests it may be related to a recent Power Automate Desktop update.

Could you please explain why these timeouts are not being enforced and why the action keeps waiting for such a long time, even though it eventually succeeds? Also, are there any known issues to prevent this long blocking behavior?

Thank you in advance for your help.

Categories:

Power Automate Desktop