Error: "Task was canceled" while connecting robot and orchastrator

[Gabriel_melo]

Hi guys, I am having this problem and I couldn’t solve on my own nor reading threads about this subject. Please any one can help me.

It all happened after my client changed some policies on their VM. After being able to connect to their VM using a VPN this error started to occur, i’ve tried some solution like restarting the service and creating another robot but none of these solutions helped me.

[Lahiru.Fernando]

Hi @Gabriel_melo

I think the robot is failing to connect to the orchestrator after the policies are changed.

Check whether your VM has a visible connection to the orchestrator machine

Check whether the required ports to connect to orchestrator are open

Also make sure you guys have access to the internet in these machines

[loginerror (Maciej Kuźmicz)]

Hi @Gabriel_melo

Does this help?

Execution has been cancelled

Hi everyone, I had this error myself. I fixed it by provisioning my robot in Orchestrator with full domain\username instead of just username in this field. So, this was not working: [image] But as soon as I changed it to this, it started working again without the error message: [image] You can get the exact value of domain\username with this command in the command line: [image] Please let me know if it fixed it for you! It seems like in the past Orchestrator would accept just the usernam…

[Gabriel_melo]

Hey guys, Thank you for your help. It was a firewall problem. To be honest I don’t know what changed since it was my client that solved the problem but it was something related to the firwall. So if anyone has this same problem as me in the future check the firewall and the connection.