Unanswered

Problem with timeouts when using RDP

(0) Share

Report

Posted on by Wereley9

Hello,

I'm new here, and english is not my first language, so feel free to correct me.

I'm having a problem when using Power Automate Desktop inside a RDP connection, all the timeouts I've tested in actions like "wait for window content" don't work. For example, after connecting to the RDP connection, I have the following action:

I've setted the timeout to 60 seconds. But, when I run the flow, it does not wait 60 seconds before fail. Here is the execution log (its in portuguese, sorry):

After only 312ms it failed.

Here are the input details of the action that failed:

{

"timeout": {

"localizedName": "",

"value": "60",

"variableName": ""

"checkElementState": {

"localizedName": "Verificar estado do elemento de interface do usuário",

"value": "False",

"variableName": ""

"containsMode": {

"localizedName": "Aguardar até a janela",

"value": "0",

"variableName": ""

"element": {

"localizedName": "Elemento de interface do usuário",

"value": ":desktopicons{<{<{<SelectorSeparator>}>}>}uia3:// > listitem[Name=\"AOS164_NOLOADBALANCE\"]",

"variableName": "RDP desktop - server - Remote Desktop Connection > Desktop Icons > AOS164_NOLOADBALANCE"

}

Can someone help me to fix this issue?

Categories:

Power Automate Desktop

I have the same question (0)

All responses (6)

Answers (0)

Deenuji_Loganathan_ 6,250 Super User 2025 Season 2 on at

Like (0)

Report

@Wereley9

Have you tried with increase your default timeout duration from 60 to something like 150 or 200?

Thanks,
Deenuji Loganathan 👩‍💻
Automation Evangelist 🤖
Follow me on LinkedIn 👥

-------------------------------------------------------------------------------------------------------------
If I've helped solve your query, kindly mark my response as the solution ✔ and give it a thumbs up!👍 Your feedback supports future seekers 🚀

Was this reply helpful? Yes No
MichaelAnnis 5,727 Moderator on at

Like (0)

Report

Just to confirm, are you using an agent inside the RDP connection?

When working in a remote environment, elements are not available on the remote computer w/o having an RDP agent installed on that computer.

Was this reply helpful? Yes No
Wereley9 14 on at

Like (0)

Report

Yes, I'm using the agent in both machines, and its syncronized. My flow works normally, but sometimes the remote machine takes longer to login, and thats when the error occurs. I didnt wanted to use just "wait" action, because the time can variate, thats why I'm trying to use the "wait for window" action.

Was this reply helpful? Yes No
Wereley9 14 on at

Like (0)

Report

Yes. At the end of the flow, it waits until a window appear to know its finished. The time this part of the process takes varies a lot, and I tried using 600 in the timeout, but the same problem occurs.

In the end, I ended up setting an "wait" action with 300 seconds of timeout. But sometimes the process takes less than 5 seconds, but the flow has to wait until the "wait" action finishes.

Was this reply helpful? Yes No
MichaelAnnis 5,727 Moderator on at

Like (0)

Report

What if you put a 10 second wait on a loop?

Loop While 1=1
If Element exists

Exit (loop)

Else

Wait 10

End (if)

End (Loop)

Was this reply helpful? Yes No
Wereley9 14 on at

Like (0)

Report

Sorry for the delay.

I tried using a "loop" and a "if window is open", but I got a "operation timed out" error:

Was this reply helpful? Yes No