I always assumed that jobs and triggers priority determines which job to launch first in case of triggering at the same time.
But apparently, they are only relevant when allocating a robot when there are a bunch of jobs in pending.
I did a little experiment.
I got two processes with the same priority. they do nothing more than to log a message.
I left an item “new” in both queues, so the triggers should fire regularly.
I get the job fired by the lowest priority trigger consistently running before the other one
The priority of queues cannot be made inter dependant..they are exclusive for items in the same queue
now coming to job priority yes it comes into picture before starting and for time triggers mainlt..queue triggers have difference as item triggers it..once a job starts the priority is lost and also try creating the higher priority trigger first and next the other one and names also give accordingly because when they are checked ideally in real time they are check one after other even if its not see like that.for postponed items
Thanks for the answer!
That’s a neat idea. Setting up a SLA automatically sets deadlines for new queue items.
Sadly, doesn’t change the triggers firing order.
Thanks for the answer.
Looks like the only way I could change the firing order for the triggers is by deleting them and recreating them in the order I want.
It’s a workaround, not a perfect one.
The job being triggered has no awareness of the items in the queue and their inherent priority.
If you want one queue to be treated as a higher priority then in the trigger you can raise the job priority, this should help make sure that job runs first, but it will then complete all the items in the queue, irrespective of priority, before finishing and letting the next lower priority job run and process its queue items.
Queue item priority only affects the next item to be processed from the queue, it has nothing to do with the job priorities.
