The Robots Already Have Pending Jobs For This Process (#1670)

News Knowledge Base
1

Error Fix for " Could not create jobs. The Robots already have pending jobs for this Process (#1670). "

Confirm if the same process is scheduled on the same Robot multiple times and their execution time overlaps, it may have scheduled for less than a min interval.

There are series of events which gets triggered when a job is triggered i.e

Windows session are created , all the Windows process, Robot executor are triggered as services and post closure of the Robot automation all the processes are stopped , memory disposed and eventually Windows session is closed.

  • For schedule as short as 30 seconds or less than 1 min, it is not a recommended approach to schedule at such short interval.
The reason "could not create jobs. The Robots already have pending jobs for this Process (#1670)." error is because one job is pending while another one is triggered at the same moment.
  • The other jobs stay indefinitely in pending , the reason being it attempts to create a windows session but it fails to do so as the existing session in being closed and it does take minimal time to for the session to close completely. This will eventually end up with windows server session related issues.

Resolution: Below are the recommendations,

Approach #1 :
  • When the same process is being executed in a loop , instead of scheduling for every 30 seconds or less than 1 min interval include a delay of 15-30 seconds as per your requirement at the end of the workflow. And again loop the workflow from the beginning.
  • This will help to rerun the execution without any impact on the windows environment as the Robot executor will be running indefinitely.
  • Doing so, the job is scheduled only once and the closure of the Job can be done by validation of datetime within the developed code.


Approach #2:
  • Include enough gap between 2 consecutive jobs.
  • Example: For a job which runs for 5 minutes should have a minimum of 1-2 minutes between each subsequent runs (30 Seconds windows session + 30 seconds unforeseen server slowness)
  • Ensure that there is enough time gap between the scheduled jobs, so all jobs can be scheduled in all the scenarios.