Hi all,

Last Friday, Issta (Israeli Tourism company) decided to duplicate one of their machines and on-board a new unattended robot. 

During on-boarding, the robot became Ghost and stuck on "Starting Robotic Mode." Reinstalling the robot didn't help.

The team handled this issue didn't want to restart the servers, since they were in production, so they tried looking into other things that might cause the problem. 

The next option they thought about was to disable credentials vault, but they didn't want to do that either since it would affect another robot that is already running as well. 

Before deleting the robot again, they checked the OS credentials and found that there are two identical credentials defined, but on two different domains (Issta and Issta A).  

The resolution was to delete the two settings and then set up only one of them. 

Thanks, @Salo Ben-Avi​, @daniel Shai​, @Dudi Grinstin​, and Yifat. 

Team - if you have any questions on this process, I think it's best to ask them here and let one of the participating team members to reply on this thread.