I was wondering how the trigger on queue works. I have a process, which only seems to start automatically if there is being pushed a new item to the queue, but not if there already are ‘new’ items in the queue.
How could we solve this?
In addition, Is there a kind of heartbeat/frequency in minutes where the process checks the queue?
It will trigger if there are already items in the queue. Orchestrator checks periodically (I think the default is every 15 minutes) if there is anything in the Queue.
However, you should build your automation so that it processes an item from the Queue, loops back to the beginning and looks to see if there is another item in the Queue and processes it, etc until there are no more items in the Queue.
“However, you should build your automation so that it processes an item from the Queue, loops back to the beginning and looks to see if there is another item in the Queue and processes it, etc until there are no more items in the Queue.”
I am certainly doing this
There is a dispatcher and performer, and a very short SLA. so preferably the performer should start up immediately, even though it loses the connection to orhcestrator and stops the job completely. “Job stopped with an unexpected exit code” ← This classic occcurs sometimes for example.
“Orchestrator checks periodically (I think the default is every 15 minutes) if there is anything in the Queue.”
Do you know if theres a way to shorten this frequency?