We faced unexpected behavior with the Queue Triggers, the trigger has been run too many times (every 30 minutes) Although there is no new transaction item added to the queue.
After investigation, we found a stuck item on InProgress status, after reading the documentation, we found the justification
Orchestrator takes into account both New and In Progress queue items when computing the number of target jobs that must be reached for optimal resource allocation.
So, any idea or configuration to excluded the queue triggers running when having an item with InProgress status?
Yes, this first time faced this issue.
Just to clarify, two items on queue have an InProgress status (due to the Robot having lost the connection with Orchestrator), this is not a problem now.
The case is why the Queue trigger mechanism running the job although there are no new transaction items?
I don’t know why the UiPath Orchestrator hasn’t a configuration to excluded this behavior by preventing queue triggers from starting when have just an InProgress items.