Encountered an error with the robot communication.

(2) Share

Report

Posted on by 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?

Categories:

Power Automate Desktop

I have the same question (0)

All responses (29)

Answers (0)

Sort by

chris2022 2 on at

Like (0)

Report
Copy link

Link copied!

Just had this also and having trouble fixing.

Was this reply helpful? Yes No
Cristpb 23 on at

Like (0)

Report
Copy link

Link copied!

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

Was this reply helpful? Yes No
Dawid_Szalanski 12 on at

Like (0)

Report
Copy link

Link copied!

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

Was this reply helpful? Yes No
wnzn 168 on at

Like (0)

Report
Copy link

Link copied!

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)

Was this reply helpful? Yes No
Cristpb 23 on at

Like (0)

Report
Copy link

Link copied!

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

Was this reply helpful? Yes No
Cristpb 23 on at

Like (0)

Report
Copy link

Link copied!

We already updated too, but the error persists

Was this reply helpful? Yes No
Slavnyy_Avtomat 108 on at

Like (0)

Report
Copy link

Link copied!

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.

Was this reply helpful? Yes No
Slavnyy_Avtomat 108 on at

Like (1)

Report
Copy link

Link copied!

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.

Was this reply helpful? Yes No
Dawid_Szalanski 12 on at

Like (1)

Report
Copy link

Link copied!

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 .

Was this reply helpful? Yes No
Cristpb 23 on at

Like (0)

Report
Copy link

Link copied!

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

Was this reply helpful? Yes No