[PAD + Virtual Desktop Agent] UI operations on RDP session stop during flow execution

(0) Share

Report

Posted on by 貴片-14010838-0

I am creating a Power Automate for desktop (PAD) flow to automate a Windows application running inside a remote PC.
I connect to the remote PC via RDP, and the remote machine has Power Automate agent for virtual desktops installed.
The UI automation is performed through the agent.

■ Issue

During the flow execution, UI operations inside the remote PC (clicks, text input, etc.) suddenly stop working
About 30 minutes after the UI operations stop, PAD throws a timeout error
※ No timeout setting is configured on the PAD actions
The flow is executed in attended mode

■ What I would like to know

Possible causes why UI automation suddenly stops working on the RDP session
Recommended settings or countermeasures ( registry, agent configuration, flow design, etc.)

■ Environment

Client PC: Windows 11 Pro 23H2
Remote PC: Windows Server 2022 21H2 (running on Hyper‑V)
Power Automate for desktop: 2.62.161.25297
Connection: RDP → Power Automate agent for virtual desktops
Execution mode: Attended

If anyone has experienced similar behavior or knows the potential root cause or mitigation steps, I would appreciate your guidance.

Categories:

Power Automate Desktop

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Srini007 3,483 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @貴片-14010838-0,

If you are running the automation with the attended license then your RDP session need to be active all the time and check with the VM administrator whether any policy that getting timeout at certain period for VM, if you minimize or auto locked then it won't work, so you need check and set the RDP to not to minimize or lock or if you can't make it then you need to have unattended licence even if the VM is closed or locked

(If this answers your question you can mark as Answered and give it a Like)

Regards,

Srini

Was this reply helpful? Yes No
貴片-14010838-0 4 on at

Like
a
(0)

Report
Copy link

Link copied!
Thank you for your reply, @Srini007

Here’s where things stand right now:

RDP session
The RDP session is always kept in the foreground, and the screen never locks, so the session should be staying active while the flow is running.

VM policies
I'm checking with the VM administrator to see if any session timeout or lock policies might be affecting this.
It may take a little time since the admin isn’t very familiar with VM/RDP policies.
Also, the timing isn’t consistent — sometimes the UI stops after about 10 minutes, other times it runs for more than 30 minutes without issues.

Unattended license
We’ll also consider using an unattended license if it turns out we can’t fully avoid session-related issues.

If there are any other possible root causes or things I should look into, I’d really appreciate any further suggestions.
Thanks again for your help!

Was this reply helpful? Yes No
Suggested answer

Srini007 3,483 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @貴片-14010838-0,

Thank you for providing more details, as you mentioned the timing is not consistent I doubt on the selector or timeout failure, you can check more on ui elements when the execution is getting stopped see that website behaviour is it that the Ui Element is not identifying correctly, since I don't see your flow I doubt on UI elements only

(If this answers your question you can mark as Answered and give it a Like)

Regards,

Srini

Was this reply helpful? Yes No