Queue trigger has an option “Maximum number of pending and running jobs allowed simultaneously” but it does not consider suspended jobs.
I have a Performer process which I need to suspend till morning if it is triggered at night, but then I don’t need new jobs lining up in suspended state due to the queue has items with “New” status.
A process can go into suspended only after starting and having some wait for resume tasks in it…so without starting it cannot come or assessthat state…if you need to stop processes after certain time then use stop after that might help…but suspended can be more than 1 a d cannot abide the rule as per the nature of the processes I believe
And suspended works on trigger from the tasks so it is not controlled by trigger
Why some of the queue items got suspended have you sent the Invoice or any other document to Action center for validation.
If yes, then After submitting the created task in action center, the bot will come back and pickup these suspended state queue item and complete the remaining steps. You have to submit the created tasks in action center then only bot will resume and execute the remaining process.
Give the number more than 1 in the Max number of running and pending jobs allowed then you will see the difference in execution.
I believe they explained, they suspend based on time.
@gediminas the triggers never factor in suspended jobs, as documented here.
I’d say you are using job persistence in an odd way.
If the queue items dont need to be actioned by morning, postpone the queue item until the required time and let the job finish. It will be triggered again in the morning once the postponed time is reached. No jobs will be triggered for any of the queue items that havent reached their postpone date.
