No. I have one queue for the performer. The dispatcher creates items in that queue. Then I have a different queue for the actioncenter process, and the performer creates items in that queue. When an item is added to the actioncenter queue, the trigger kicks off a job. The actioncenter process creates the task then waits (suspends).
Dispatcher → performer queue
Performer → actioncenter queue
When I say actioncenter process, I literally mean a separate project. So I have MyBusinessProcess-Dispatcher, MyBusinessProcess-Performer, and MyBusinessProcess-ActionCenter as separate projects/automations. The first two loop, the actioncenter one does not.
That’s not correct. You don’t wait for one job to finish before starting the next job. You set up the Trigger to create MULTIPLE jobs at the same time (for the actioncenter process). That way if 5 items go into the queue, 5 jobs are started.
I usually set this, also:
Just makes sense to me (for permissions and other reasons) to have it resume under the same robot/server. But in the end that depends on your needs and environment.
So you end up with multiple jobs suspended waiting for the task to be completed:
How many jobs it creates is up to you, your licensing, etc. However keep in mind when a job suspends it is NOT using a license.