I may or may not answer my own question here…
We have the dev robot setup on a VM, we create a job in orchestrator via an API call. Robot Starts and Closes remote desktop to the VM. If we recreate the connection quick enough we can witness the bot working.
Is this behaviour because the bot is unattended when triggered by orchestrator? the Bot is setup as unattended. Is it this that causes us to be booted out of the VM?
We only want to be able to see the bot working as we are creating a demo using another piece of software and uipath together on the VM.
If we start the job manually directly from the Bot itself we do not get boot out of the remote desktop