Power Platform Community Forum Thread Details

This is the error message I am getting ... Action 'Run_a_flow_built_with_Power_Automate_for_desktop:_Quote_Fufillment' failed: No machine able to run the automation has been found. Aborting execution. Error encountered when connecting to machines: There is a user session on the target machine. Cannot execute unattended desktop flow.

My cloud flow is triggered by outlook which ultimately launches PAD. The machine that is running my PAD is connected to our server and only dedicated for this workflow. There is no other session on it currently, so I am unsure why I keep getting this message.

Categories:

Building flows

This specific error usually means your desktop flow is set to run Unattended, but Windows still recognizes an active user session on the target machine. A disconnected RDP session also counts as “active.” Power Automate won’t start an unattended run if anyone is signed in, even if the screen is locked.

Here’s a simple checklist to fix it and prevent it from happening again:

1) Check for User Sessions on the Windows Machine where PAD is supposed to run.

On the target machine (or via RDP once), check for lingering sessions:

Open Task Manager, then Users, and verify that no users are signed in. If you see any, right-click and select Sign off.

Or use an elevated CMD:

query session lists sessions

logoff <ID> signs out a lingering session.
(Do not just close your RDP window; that “disconnects” and keeps the session active. Always sign out.)

2) Confirm machine status in Power Automate.

In the Power Automate portal:

Monitor or Data, then Machines/Machine groups.

The machine or group used by your connection should show Online and Unattended - Ready.

If it shows In use or Attended, there’s still a session.