Power Platform Community Forum Thread Details

We are facing an issue where Power Automate cloud flows are no longer able to trigger desktop flows on a registered machine.

Until yesterday evening, we were able to successfully run the desktop flow in unattended mode for testing. However, after that point, the same cloud flow triggers no longer start the desktop flow execution.

Key points:

Both Attended and Unattended modes are affected.

The cloud flow is triggered successfully, but the desktop flow does not start on the machine.
No changes were made to the desktop flow code, cloud flow logic, or machine configuration when the issue started.

We tried the following troubleshooting steps:

Restarted the VM multiple times
Restarted Power Automate services
Killed all existing PAD sessions
Re-registered the machine
Rebuilt and replaced the VM

After re-registering, the machine worked for only 2 runs, and then the same issue occurred again.
One other bot is running successfully on the same VM and machine, which suggests this may be a machine/session or service-level issue.
In some cases, the machine shows “Status unavailable” or machine settings take a very long time to load in Power Automate portal.