Unanswered

UIFlowsAgentCommunicationFailure when running cloud flow

(1) Share

Report

Posted on by ML2020

Hello,

I have an issue when trying to manually trigger a flow using cloud flows and I hope someone here can give me a hand on this 🙂

Error message:

{
 "error": {
 "code": "UIFlowsAgentCommunicationFailure",
 "message": "Something went wrong with the desktop flows app on your machine. Try running this desktop flow again."
 }
}

Status code: 400

The flow is just as simple as it can be - just run Contoso Invoicing App. That's all. Now when I run the flow from Power Automate Desktop it works just fine and ends correctly. But when I try to invoke this flow using Cloud flows, it runs (Contoso Invoicing App opens) but then it seems to be stuck for 2 minutes on status running and then fails with error message provided above.

I checked the On-premise gateway - it says the gateway is online and ready to be used. Network ports test also ended with success so it seems everything should communicate without errors.

Reinstallation of both Power Automate Desktop and Gateway didn't help obviously.

I am running on Virtual Machine with W10 Pro x64.

Any ideas?

Thanks in advance.

Categories:

Power Automate Desktop

All responses (10)

Answers (0)

Sort by

john-dund Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hi ML2020,

Can you confirm what version of Windows you're using? Are you using Windows 10 multi-session by chance? Can you also let me know what version of UI flows you're using? If you're not using the latest version (2.2.128.20340), can you please install the latest?

Thanks,
John
ML2020 8 on at

Like
a
(0)

Report
Copy link

Link copied!

Hello John,

Thanks for reply. Answering your questions:
System edition: Windows 10 Pro, 64 bit, x64-based processor
System version: 1909

I am not using multi-session. Virtual machine runs on my local computer via VirtualBox version 6.1.16 r140961 (Qt5.6.2)

About UI Flows, I am using the latest version (checked today):
Power Automate Desktop version: 2.2.20339.22608

I also checked the gateway - its in latest version:
Gateway version number: 3000.68.15

Regards,
ML
john-dund Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

I will follow up with you in private message to investigate this with logs.

Thanks,
John
ML2020 8 on at

Like
a
(1)

Report
Copy link

Link copied!
Case is solved, thanks @john-dund and @FRH for support.

It looks like there was a problem with corrupted performance counters on my VM. Executing the following command via cmd in admin mode was the solution:

lodctr /r

Regards,
ML
john-dund Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Thanks for posting ML. We have also fixed this on our end so that future releases of Power Automate Desktop should not fail runs with machines in this state.
asbpowerbi 26 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi John,

Can you tell me where the log files are located. I too am running into this issues, however I am running on a Windows Server device.

Thanks!
john-dund Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

hi asbpowerbi, just to confirm, you're getting the "UIFlowsAgentCommunicationFailure" error? And you're getting it consistently? Are you using the on-premises data gateway or connecting directly to the machine?
asbpowerbi 26 on at

Like
a
(0)

Report
Copy link

Link copied!

I am using an on-premise gateway.
john-dund Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Can you try using direct machine connectivity? This is the recommended approach.
asbpowerbi 26 on at

Like
a
(0)

Report
Copy link

Link copied!

Thank you for the reply. Forgive me, I am using Direct Machine Connectivity, not a gateway. The computer is registered. The UIFlowService service is running. In the PowerAutomate machine runtime application, I found a way to export the logs. The exported zip file is 10M and too large to upload here. The failures occurred on 1/4/23 at 3:00am and again today 1/5/23 at 6:27am. What should I look for?