We have observed that randomly a Queue Trigger just stops working. It is not disabled.. Runs one day and then not the next. Sometimes if you disable and enable the trigger it will start working again, but many times we have to remove the Trigger and recreate it entirely. Even then, they May or may not work or will occasionally work for period of time then stop again.
Hey @FL.Duck
Orchestrator has a built-in “circuit breaker” that automatically disables a trigger after a number of failed job-creation attempts. By default it’s 10 failed launches within 1 day.
You can see and adjust this under Tenant → Settings → General → Execution Settings – like in the screenshots:
2 Likes
just to complement and check @pikorpa suggestion you can go for trigger history.
Also look for the queue setting where you include how many pending and running jobs are allowed. All these settings can influence in your trigger..
1 Like
Great information, thank you. The trigger actually never starts the bot so the history is blank other than being created and when I updated it by disabling and enabling it again. The triggers never move to disabled, they just don’t fire..
@FL.Duck
It seems it’s not the “circuit breaker”.
There was a very similar case on Cloud where the issue went away after they simply created a new Process from the same package and a fresh queue trigger:
- When you say not working is the new items addition to queue not triggering the bot? or are those some items which are postponed and got active now?
- Also recreating process and trigger fixes this issue most of the times
cheers
1 Like
Weird issue, I have never heard of the triggers not firing.
If possible I’d try to sandbox it and make it repeat, or when it does happen leave it in that state and make a ticket with UiPath support, they’ll need to check what is the issue in the background.
Most of the time a new queue item triggers the bot. This can work fine for a long time. randomly one day a new queue item doesn’t trigger. There is no record of any change to the trigger, and no job is started. The solution at this point is sometimes to just disable and reenable the trigger. Many times this will not work (even after the 30 minute cloud cycle) and I have to remove the trigger, create a new one that is identical and it fires right off.
can you check if there is any pattern like for any specific type of queue items or after any updates
those are very rare scenarios but if it is occuring often I would say better raise a ticket with UiPath they can check from backend if the trigger was disabled or so
cheers