What is the root cause of alerts "Trigger could not create a job as the maximum number of jobs has been reached"?
Issue description:
This knowledge article provides insight into an error message relating to job creation in UiPath: "Trigger could not create a job as the maximum number of jobs has been reached". The error occurs due to exceeding the limit of running or pending jobs set within the system.
Error:
"Trigger could not create a job as the maximum number of jobs has been reached"
Root Cause:
The root cause of this error is that the current settings may have been configured in a way that for each new transaction item, a new job is created, and for every subsequent transaction item, a second job is initiated, with simultaneous running or pending jobs set to one or two. Once this limit is reached, the system is unable to create any additional jobs.
Resolution:
- Recognize the current setting system where, for every new transaction item, a new job is created. For every additional transaction item, another job is initiated, with a simultaneous running/pending job count of 1.
- Implement a change in the simultaneous running/pending job count to 2 and increase the number of transaction items necessary to start a second job to 10 or 50.
- This change ensures the first job begins at one transaction item, and the second job only starts or remains in a pending state until the creation of 10 new transaction items. This provides enough time for the first job to continuously initiate new items.
Updated Settings:
- Minimum number of items to trigger the first job: 1
- Maximum number of pending and running jobs allowed simultaneously: 2
- Another job is triggered for each: 10 or 50 or more transaction items