Queue Trigger Alerts

There have been created the Queue triggers for executing a queue items. The Jobs were executing but an extra alert mail has been sent to users as below .

#process -------------- could not create jobs. The maximum number of jobs for this Process has already been reached (#1693).

Does anybody have any ideas why is this sent or how can we avoid this alerts.

@thsundar - specified alert will trigger only when a process job already in running state-> and a new (1 or more) process job(s) created.
pls check the job creation process in orchestrator (when one job is in running state (same machine/same robot user) - new job should not create)

Our queue triggers settings made was
Minimum number of items to trigger the first job : 1
Maximum number of pending and running jobs allowed simultaneously : 1
Another job is triggered for each: 1

Which means default one. We have also tried changing the minimum no of items to triggers first job to up to 7, but still the alerts triggers for each queue items.

But it is processing successfully

@thsundar, I am having the same issue with my QUEUE triggers as well… Have you found any way to fix this error?

What version of Orchestrator are you using?

@s3vn, I have modified parameters of queue triggers as below

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: 50

so my second job had no chance to start . Tried this and monitoring the case still now not getting alerts.

Let me know if it helps for you .

1 Like

I thought about making that same change. I updated my queue trigger and will let you know if that fixes the issue for me too!

@thsundar, it looks like you found a fix to the issue. I haven’t received alerts since I changed Max jobs to 2 and Another Job Triggered to 100.

Thanks!
s3vn

PS. I think this may be a bug in Orchestrator though, cause it doesn’t read like it should work that way.

It solves the alerts issues but we should know what will happen if we fix the count of 2 job to trigger to 50 or 100 in future cases if the bot is handling more no of queues.

So UiPath team should be aware of this or we should remind them .

If you are licensed for an enterprise version of UIPath you can submit a support ticket…maybe they will have a more definite answer for us.

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.