Having an Issue with Queue Triggers in Orchestrator

Help Orchestrator
,
1

We have a Queue Trigger set up to have a Maximum number of pending and running jobs allowed 3 and After completing jobs, reassess conditions and start new jobs if possible. I have found in Automation Cloud that these settings do not work as they should. Only one job is starting and after it completes it does not pick up the next queue item. If I manually start the process I can get three to run, but then it does its 30-minute wait time to run again.

Is anyone else seeing this same issue? If so, were you able to resolve it? I wonder if I delete the Trigger and recreate it if it would work again.

The image shows a configuration screen for setting up a queue trigger named "EB Posting Performer," which includes options for triggering conditions, job limits, and timezone settings. (Captioned by AI)
The image shows a configuration screen for setting up a queue trigger named "EB Posting Performer," which includes options for triggering conditions, job limits, and timezone settings. (Captioned by AI)703Ă—596 34.4 KB

2

@PWilliams

Can you be more clear

it looks like queue trigger…

did you assign any machine or user?

also what is the queeu trigger interval cofnigured?

go to tenant → settings → general

at the end you would see trigger related settings…please check them

cheers

1 Like
3

Hello @Anil_G !

Thank you for the reply! I reviewed the settings. We do have machines and user/robots assigned to the folder to run the jobs. The queue trigger interval is set to run every 30 minutes. I have updated the setting to 15 minutes. Thank you for that info!
However, it did start picking up more than one at a time. I did not do anything to change this, it started working on its own. :man_shrugging:t4:

1 Like
4

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