CRON job did not run
The cron was :
0 */12 * * *
The UI is reporting something correct
I changed the cron by 0 0,12 * * *
It did not work.
the cron never starts at 12 AM, no idea why, the ui shows it will but never does..5 Replies
Project ID:
7fc7bc42-6e0c-449e-92b2-6706b93a05927fc7bc42-6e0c-449e-92b2-6706b93a0592
Service: 762ab55e-21cc-4135-bf44-94a775ea4884
There is nobody to answer a cron question ... ?
@Ray is there anyone checking the cron ? it is a simple nodejs script, run for a minute and
process.exit(0).
it runs at 12 pm but never starts at 12 am. is the cron a reliable solution here ?Do not ping the team. This server is community help, you’ve been told before to be patient
the majority of us here are in EST, we are not going to be around to answer your questions at 4am
0 */12 * * * runs it every 12PM. If you want everyday at 12AM, use 0 0 * * * instead.
And in the future, please keep in mind:
- this is community support - you should not expect immediate or fast answers
- do not ping a team member/conductor again -> #🛂｜readmeHello, sorry for the ping.
thank you for the answer. The error happened during the outage; I was not sure if it was related to the outage, so I created a second request, to avoid confusion. I understand now this is a community help, I really thought it was a pro one as I have a pro (team) membership.
Btw,
0 */12 * * * means at 0:00 (UTC) and 12:00, it was only working for 12:00 and displaying it would run for 0:00 but never did. I tried 0 0,12 * * * but it did not work.
I tried now 1 0,12 * * *, it seemed it worked but still.
I am here testing a feature not working well, the next run is showing a time not respected, the 15 minutes threshold is not shown in the ui, works sometimes under 15 minutes, confusing for a cron running a script.
Thank you for the help though. Now that I knoww it is a community support, I will approach my ticketing differently. This ticket can be closed.