Scenario:
We have multiple processes built, which start their jobs based on timed triggers. We have more jobs than robots so once in a while the jobs are pending to start. No problem so far.
Our unattended windows environment starts by the UiPath Orchestrator triggering a windows login, then runs the job, and after completion logs off the windows session. Still no problem.
The problem occurs in the next job. Dynamic allocation favours the first available Robot according to a fixed sequence. (The order of creation it seems). This often means that Bot1 runs a process and completes it, and once done immediately starts the next pending job. And this is where the problems start.
The end process reports to the orchestrator that the job is completed and the Robot available, while in fact this robot is still completing log-off activities and session ending on our workspace server. The next immediate start of the new job on this machine results in an ‘access denied’ error, failing the eintire job, simply because windows wasn’t available yet.
Queueitems have retry capabilities, but entire jobs don’t.
Double scheduling of jobs can cause operational issues so this is no option, and dynamic allocation of jobs on Robots is a requirement.
Does anybody have any advise on how to solve this synchronisation between orchestrator and workspace status?
It seems that you have trouble getting an answer to your question in the first 24 hours.
Let us give you a few hints and helpful links.
First, make sure you browsed through our Forum FAQ Beginner’s Guide. It will teach you what should be included in your topic.
You can check out some of our resources directly, see below:
Always search first. It is the best way to quickly find your answer. Check out the icon for that.
Clicking the options button will let you set more specific topic search filters, i.e. only the ones with a solution.
Topic that contains most common solutions with example project files can be found here.
Read our official documentation where you can find a lot of information and instructions about each of our products:
Meet us and our users on our Community Slack and ask your question there.
Hopefully this will let you easily find the solution/information you need. Once you have it, we would be happy if you could share your findings here and mark it as a solution. This will help other users find it in the future.
Thank you for helping us build our UiPath Community!
Based on the description I would look at the UiPath_SESSION_TIMEOUT System Environment Variable, I believe the default is 30 or 60 seconds and if the session is taking longer to logout it can prevent new sessions from being created.
Anil_G
ashokkarale
jinal.shah
Gautham_Pattabiraman
postwick
chandreshsinh.jadeja
vrdabberu
Ajay_Mishra
sven.wullum1
Vyshnavi_Nalumachu