Encountered an error with the robot communication.

[Dawid_Szalanski]

I'm getting an error while executing a process in PAD. 

Connection is directly to machine (VM) and process is in unattended mode. 

Has anyone had a similar problem and knows the solution?

[chris2022]

Just had this also and having trouble fixing.

[Cristpb]

we are having the same problem, in unattended mode. And when we run it in attended mode, it shows the same error.

[Dawid_Szalanski]

How did you started your robot in attended mode, via cloud or directly from Power Automate Desktop?

[wnzn]

Same issue unattended mode triggered by cloud flow. It is intermittent, some flow runs work some don't. Support advised to upgrade to 2.23 but to no avail. Even worse, it introduced another issue: Picking UI element don't work anymore - Power Platform Community (microsoft.com)

[Cristpb]

I started the flow via the cloud, but I was watching the machine via remote desktop

[Cristpb]

We already updated too, but the error persists

[Slavnyy_Avtomat]

The error spread to running attended for us on top of the Unattended failure.  I wish the error provided more information so that we could troubleshoot it as a community.

[Slavnyy_Avtomat]

I'm copying my response to my thread -- open a new automated flow in PAD 2.23 and copy over the steps from the current flow and you should be good.

I wanted to do more in depth troubleshooting, so I rebuilt the flow that failed to run in attended and unattended modes.

I'd created a blank template and pasted the subflows over, testing as I added them.  Rebuilding the flow using the steps pasted from the broken flow has resulted in a success.  It can now run attended and unattended.

If I had to guess as to a root cause, I'd say that it's something in the translation from 2.16 > 2.18 > 2.21 > 2.23

Regardless, issue appears to be resolved.

[Dawid_Szalanski]

I have this issue on 2.20.141.22151 and 2.21.262.22194. After update to 2.23, recommended by MS still the same. I will try to copy like @Slavnyy_Avtomat .

[Cristpb]

I copied the functions here for a new automation, but the error persists. It didn't solve the communication problem.

[Cristpb]

Hello. Friend, did you happen to solve this error?

[psatpute]

Hello All,

I too am facing the same issue and the version of PAD we are using is 2.18. But from the discussion on the forum, it looks like updating the PAD version won't help. One thing we observed is that the error falls under the category "Robin Agent Faulted", which you could see in Power Automate cloud > Monitor > Desktop flow activity (preview). Not sure what that is and have not seen any article/post explaining this.

Can someone please help me in understanding what the error is as it's very vague and does not explain anything?

A solution to this will be appreciated. Thank you!RobinAgentFaulted

[Cristpb]

Very well observed. Now that you mentioned that, I looked here and there is also this "error" of RobinAgentFaulted in Desktop Flow Activity. I'm waiting for a solution too.

[psatpute]

Hey @Cristpb ,

It sounds weird but can you try deleting all the "Display Message" actions (Enabled / Disabled ) from your desktop flow and keep monitoring? Post doing this, it has been like 3 weeks and I have not got the Error. Seems like it is working for me.

Can you please try the same and share your feedback.

Thanks!

[wnzn]

@psatpute My flows do not have those actions in them.

[wnzn]

I'm still facing this issue. Microsoft support has once again advised me to update to 2212 which didn't fix the problem and has added a few others. 

[psatpute]

@wnzn Can you recheck once in your flows, because the DISABLED Display Message Actions too needs to be removed. For me I have not received any such error post removing the "Display Message" actions (The one's which were is my test subflows as well as the one's which were in disabled state). 

[wnzn]

There are no such actions in the flow definition, not active nor disabled. I'm still engaging with support and will update when I have news.

[FredTheRed]

Have you heard something? 

I'm having the same issue. And it almost happens at the same time, which is frustrating. 

And we have just updated to the lastest version on all servers.