Hello @UiPath_Community and UiPath users,
I want your help, today the job has to be triggered, but suddenly the triggers are disabled, I have checked the audit logs but nothing was found, but when i enabling the triggers, it failing with below error.
Please check the jobs ran before and see the status. If there are continious error for all the jobs triggered for the scheduled trigger - It will be disabled automatically based on the configuration in the UiPath config file.
If the continious error is the issue - fix and schedule after that
Hi @sharazkm32 ,
Thanks for your reply, the job has been triggered at the correct time. But the triggers were disabled. I’m not sure whether the triggers are disabled after the jobs triggered or not.
Does the job run’s due to schedule were success / failed / faulted?
As per my knowledge - It would be automatically disabled if the transactions got failed continiously for all the triggers
Please check whether the job or transactions were failing continiously or not
Also please share the schedule details
Hi @sharazkm32 ,
The transactions are successful.
At 11:30 AM, on day 11 of the month, only in April, only in 2025(CST)
Will the triggers disable automatically after the start of Job?
No
Ideally it wont
Unless someone manually disable or some API run’s in the background
Please share the schedule screenshot to see how it is scheduled
As per schedule - it is scheduled to run only on April 11 2025
If you are expecting to run every month, modify like
0 30 11 11 * ? 2025
This could be the reason why it got disabled after todays run
It has to be run on that particular day only.
It ran and then disabled rite ??
Because 2025 April 11 is a past date and never gonna happen again
So whats the issue here ??
if it needs to run every year - change it to
0 30 11 11 4 ? *
Also if it didnt ran today 11.30 AM , change the time to future and try scheduling
0 30 11 12 4 ? *
Hi @sharazkm32 ,
Yes it ran and disabled, Here my doubt is , are this kinds of triggers disable automatically after the job start
I am not sure whether there was any recent update
Previously - the expected behaviour was
I can try to replicate. Please share the version and environment details
Hi @sonaliaggarwal47 ,
Its a Cloud Orchestrator.
Hi @ADITYA_T,
By any chance, did you enable any of the options highlighted while creating a trigger?
Also, i think why you got the above error(your screenshot) while trying to enable the same,is because its not a valid trigger and cannot run ever per the current schedule in there. It was one time trigger which is done so if you want to re-enable it, i am guessing you would have to first edit the trigger to a date time in future and then you should be able to enable the same.
Regards
Sonali
Hi @sonaliaggarwal47 ,
No. I haven’t enable any of them. I think you are right, as the time passed out with respect to the trigger and the job was triggered and executed. But my question is are these kinds of triggers will be disabled automatically after the start of job.
i am guessing that is expected behavior even though its not specifically mentioned anywhere in documentations.
But that’s how the behavior is.
And also 1 thing to note here is that if keeping it enabled automatically was possible then you would have been able to enable it manually also after it ran also and not get the error you are getting.
It got automatically disabled because its not possible to keep the trigger enabled if it can never run, right? Or lets say if its configuration is not valid( there is no future date or time)?
But, if you are not convinced, then you can try to test it once more by creating a one time trigger and see if it gets automatically disabled. In my view, it would as same error would be thrown internally as well during an attempt to not let trigger disable automatically.
Hope this helps.
Regards
Sonali
Also, 1 more test you can do.
Try to create a trigger with past date and time. you won’t be able to do so as its invalid.
