Has anyone experienced a situation where triggers set up in Orchestrator are not working? I have tried using cron experssions but still having issues with the trigger not starting up.
I have one trigger set to kick off at 30 minutes, every two hours.
Any suggestions or ideas as to how to get this resolved would be greatly appreciated.
Thanks in advanced.
The issue should be most probably in the
First try to make a simple schedule, like to run a bot every minute without
This will confirm you if triggers are working fine, then we can try for the
cron. Also please show your settings and
cron expression to validate once.
The issues starting happening with the simple schedule. I switched over to cron expression to see if that would make a difference. Below is a screenshot of the trigger settings. We have another process that is also experiencing the same trigger issue. I have also attached screenshot with the cron expression.
I can see both screenshots having cron expression only.
Also, kindly confirm if you are using cloud or on-prem orchestrator
Yes, right now we are only using with cron expressions. The same is happening for both ways.
We are using on-prem orchestrator. We have also opened a ticket with UiPath Support.
@kimberley.mcdowell Does it showing any error. Also, did you try running the job manually, without any triggers
Yes, everything runs perfectly fine when we trigger the job manually, it is just not able to automatically start on it’s own.
I did notice, however, when I switched from simple scheduler to cron it was working fine for a while, but then later in the evening, it stops starting up automatically.
@kimberley.mcdowell Did you check the logs in Orchestrator after it stops in the middle
Sorry, to clarify - in the evening it doesn’t start up automatically, we have to manually trigger so no logs present.
So is it only in the evening ?
Also if you can check the event logs from the orchestrator server please?