I have a process running perfectly with version ‘1.0.20-alpha.150’. I have made a few updates to the code and published a new version with the name ‘1.0.20-alpha.168’ as the final published code, by uploading the nuget package.
The issue is when I submit the job for execution on Orchesterator, it gets stuck at running state and later results in a faulted job. When I switch to the previous older version 1.0.20-alpha.150, it executes perfectly okay and shows logs too, but not if I upgrade the process to a newer version.
If it shows aomething like package missing or could not download then that means the new package is not installed properly…you might need to check the firewalls on the system
They might be blocking new package downlaods
we assume the job was started in orchestrator and should be executed by a bot / executor machine (a typical unattended scenario)
Go to the unattended Bot machine and check the Windows Events log for UiPath entries. In such problem scenarios it has very high chance to help for the problem analysis
Yes, I did test in the studio and it executes correctly, then I published the code and uploaded it to the orchestrator.
Then I try to execute it by submitting the job, but it fails to complete and no logs for that job, it resulted in a faulted job with the below message:
* Info: Job faulted due to service shutdown.
But if I switch to previous working version, everything works fine.
Please try this :
1 . Try to edit selectors ( select the Ui elements once again)
2 . If it is an Unattended process, you can try remote debugging to check what is exactly happening .