I am executing the process from 1 server and which is running fine on orchestrator. When I am running that process on other folder in orchestrator and executing on other server, it is failing right after start. I am not finding the reason . Can someone help me here ?
Is it giving any error or something as it’s faulting the job?
Hey @pari_patel
It sounds like the process is failing right after being triggered, which could mean the robot is unable to start properly on the second server. One possible cause is that the user account assigned to run the process doesn’t have proper access to that machine - for example, RDP permissions, an unconfigured password, or the robot isn’t correctly linked to the machine in this folder.
Could you check the job logs in Orchestrator and see what error shows up right before it fails? That would help confirm whether it’s a permission issue, robot setup, or something else.
Here is the log. no other details showing up. Other processes run successfully on that machine.
@pari_patel
It looks like the robot is working - but the process ends almost immediately.
Are you sure that the workflow hasn’t a condition that causes it to stop early (e.g. if no data → then exit).
Maybe you use the queue with no data in current folder?
Hey @pari_patel can you check that particular folder queue because this condition comes when there is no transaction item in the queues.only in that condition the process goes in the end state . or can you try to run your process in debug mode might be some issue is having in the init state which might cause the error and your process goes in the end state .
cheers
I am not using any queue. It starts with open browser activity and then work on that browser to get the files.
@pari_patel
Do you have all the required input arguments set?
It might be worth comparing the argument settings with the folder where the process runs correctly.
Another thing to check - is the browser you’re using properly installed on that second machine, and does it have the UiPath extension enabled?
Yes, it has the UiPath extension enabled as other process use the browser.
@pari_patel
If everything is installed correctly, then the next best step is to enable job recording in Orchestrator. That way, you can visually check what the robot is doing before it exits.
Ok, will do that but where can I see that video ?
@pari_patel
in Jobs tab → 3 dots, here:
@pari_patel
Just to confirm - after enabling recording, did you re-run the job? Recording only works if it’s enabled before the job starts - it doesn’t apply retroactively to jobs that already ran.
Also, it’s worth checking whether there’s any condition in the workflow that causes the job to end silently without logging an error.
I checked and there is no condition which prevent the job to end. also I am not re-running the previous job. I am starting the job from Processes . Somehow I can’t see the video.
Is the job showing as successful?
What did you define as the entry point in the process?
I attached the error Screenshot. If soemone can help here.
Hey @pari_patel
Thanks for the screenshot - this type of error usually appears when there’s a mismatch between the robot version and the version of UiPath Studio used to publish the process. Can you please confirm what Robot version is installed on both machines ?
Also, here’s a similar case reported earlier that might help:
