Hey, I’m having issues running a process on an unattended bot in an Orchestrator Tenant. I have no issues launching the bot from my DEV Tenant to my Development Bot on my local machine, but running the process in the STAGE Tenant on an Unattended Bot is giving strange issues…
When I run the bot, it’s almost as if it won’t complete the init sequence. Many things throw
Object not set to an instance of an Object errors. The package I uploaded to the STAGE Tenant included an “Error Output” Folder that I push screenshots of errors to, this file path (referenced via my Config file) is giving the
Object not set to an instance of an object error, however, if I RDP into the machine, it begins working as expected (different user account than my local Development Robot account).
Additionally, during the login sequence, it cannot recognize any of the elements that it can on my local machine (the selectors are dynamic and are NOT the issue). So it errors on login, then tries to re-init the login after taskkilling chrome, but continues to error on this step before going to the next Transaction Item (every item fails). Again, if I RDP into the machine MID PROCESS it begins working flawlessly…
I have the launch options for the robot set with the same width/height as my local machine so it should be rendering the display correctly and thus not creating any issues with the selectors.
Anyone else have strange issues like this? Any advice on how to address this??