Can someone help me by telling me if when one uses the orchestrator for the first time in the Studio 2023.10.3 version and robots developed with advanced packages belonging to the studio 2023.12.0 community edition version are uploaded.
Should the robots be modified with classic packages so that they run the robots well from the orchestrator?
I ask this because during the last year I developed several robots in the studio 2023.12.0 community edition version and these were executed from the assistant and a week ago we acquired the unattended one so that these can run alone, but, at the time of publishing them in the unattended the robot does not execute correctly.
I attach a screenshot of how it was developed before and how it had to be changed so that it would run unattended.
Orchestrator doesn’t run jobs. The Robot.exe process on the server runs the job. When you say they won’t run unattended what do you mean? Are you getting an error? You have to give details or we can’t help you.
Basically, when I try to run from unattended, the old solution seems to start but it doesn’t even open the browser and the bot crashes, but if you run the option now, it opens the browser and follows the rest of the process.
There could be issue with the core packages in your solution/bot because no software provides 100% forward compatibility.
You developed the code in higher version studio 2023.12.0 and opening or running in down version would require core packages/packages used to downgraded to Studio 2023.10.3 required version
This is not true. 2023.12 and 2023.10 are close enough in version not to cause any issues.
@Melanny_Herrera_Cruz what is the error you’re getting when it tries to open the browser?
Is the UiPath version on your machine the same as on the server? Did you install UiPath on the server in Service mode, not User mode? Did you install and enable to browser plugin on the server? Have you logged into the server manually with the robot account? If so, stop doing that - go back to the server, log in as the robot, then SIGN OUT from the start menu. Now try running your job.
