Hey, I have a very simple scenario: one unattended robot connected to a cloud orchestrator on platform.uipath.com. I’m starting jobs using the API. Today I’ve configured a robot with the wrong user password (I mean the Windows user password) and I had the surprise that it worked. I’ve deleted the robot, re-configured it again with the wrong password and it still works. I’ve checked that the same behavior did not apply for 2019.4.4 but now for 2019.10.0 it works.
So, is this intended behavior or a bug? Or is the password now needed only when the robot has to actually create a new session? (I’ve only tested in a logged in session)