and more in a single search tool across platforms. Read the announcement here. |
04/20/2023 10:17 AM
Attempted to schedule a job to run every hour, on the 30 minute mark (30 * * * *).
Updated job through editor, job completely vanished. I am able to schedule jobs to run every hour on the hour, but scheduling on the 30 minute mark seems to anger our tenant.
Anyone ever observed this or is this fd ticket time?
Solved! Go to Solution.
04/20/2023 10:46 AM
Hi @flegare ,
Greetings.
Are the triggers not visible in the job control panel(job trigger search) after you schedule it to run every 30 mins??
Could you please try to schedule a trigger with below cron expression and let us know if you're still not able to see the scheduled trigger.
0 */30 * ? * *
Thanks,
04/20/2023 10:54 AM - edited 04/20/2023 10:57 AM
Hi @pruthvi_t ,
Thanks for the quick reply. When I provide this cron config either through the job "edit" form or the "Update Schedule" action, the job remains on its existing schedule, which is every 30 minutes at the moment. At least, the job isn't vanishing so there's that...
04/20/2023 10:59 AM
Hi @flegare
It seems issue with the cron expression. Please use below link to build your cron expression
https://www.freeformatter.com/cron-expression-generator-quartz.html
Below link can be used to check when the job will run based on the cron expression.
Thanks
04/20/2023 11:11 AM
Thank you for the cronmaker link!
Right answer turned out to be: 0 30 * 1/1 * ? *
04/20/2023 11:13 AM
@flegare ,
Looks like the issue is with cron expression being used initially.
Thanks for quickly validating and confirming.
04/20/2023 11:15 AM
Yeah, clearly the cron generated through another tool caused some heartburn to Saviynt. It is a bit sad that it made it wipe out the job altogether. But this one is solved, thanks for your assistance!