The docs for Orchestrator are for the Enterprise edition, which might make it confusing.
Basically, it is not reliable to run an unattended automation on Community Orchestrator together with Community Studio and Robot. This is due to how robot service works on the Community Edition - it will not allow you to log in into the session on the remote machine unless you are already logged in.
There will also be issues with automating on the locked screen.
Having said all of that, running process from Orchestrator in an attended scenario should be rather easy (with you looking at the screen of the machine running the automation).
Simply connect the robot to your Orchestrator following this tutorial:
And then run your process. I would advise you to go through the Academy trainings - Foundation and Orchestrator to understand the basics.
I think i failed to get you understand my issue. I already successfully connect my robot (development type) to Orchestrator on remote desktop using machine key and Orchestrator URL. And Whenever i am running my job through Orchestrator, remote machine is already logged in (no lock screen) and session is available.
BUT When I starts JOB from Orchestrator, ROBOT (deployed on remote computer) only can able to successfully execute my first activity “Start Process” and then it throws me error “Cannot find the UI element corresponding to this selector”.
When i run same process through Ui Path Studio using debug mode, every activity runs perfectly (it highlights each anchor and tag perfectly in debug with highlights) and whole process executes without any exception.
Apart from all above
WHY can’t i run my development standard robot other activities apart from “Start Process” on remote computer through ORCHESTRATOR? WHY?
Orchestrator Settings -> Deployment tab , should i need to do any settings here?
Did you check the image resolution after making these changes? If that is same as running in attended mode then I would suggest to try other Ui activities like open any application and clicking or typing something there to isolate if the issue is with Ui elements or CV activity.
(sorry I forgot to clarify - By attended I meant running from studio or robot when you are logged in manually)