We still have an environment running Orchestrator 18.3 so I’ll try and help you out if you still need assistance, but the general things to check out remain the same from 2018 to the 2020.
- Machine is created with a matching Name of the intended host.
- UiRobot Service on the host is registered to Orchestrator using the correct Machine Key
- Robot Record is created and assigned to the correct Machine, as well as the correct Robot Type and the Username is in the format domain\username
- Robot is a member of the Environment
- Process is published in an Environment that Robot is a member of
- Enough licenses / runtimes allocated
Based on the information that you provided, my first guess is the Robot is not a member of the Environment that the process is published in. If this is the case the job when initiated will be in a Pending / Pending allocation state.
When you are logging into the host are you logging in as yourself or are you logging in using the credential that the Robot would be using? Depending on your setup and configuration, it might not show the correct status unless you are logged in as the user with an existing Robot Record in Orchestrator. If you hover over the status message from the Robot Tray, it should provide you with a bit more information to guide you.
If you can provide more details about your setup and configuration of Orchestrator and Robot, we could provide more insight to help you out.