2 years ago
Hi
I have a cron job that should run every hour 0 * * * *.
For some reason, it skips runs sometimes. In the attached picture, it skips 10 PM and 3 AM, but I had cases in which it skipped 3 hours straight.
The cron job takes data from a sql database every hour and sends an alert based on a condition.
Is there any documented reason for this happening? I have another job that is scheduled to run every 5 minutes and it does so without any issues, there are no runs skipped.
Project ID:c84bb5be-0280-4c9f-92d4-910475505789
14 Replies
2 years ago
This is probably due to their over scheduling bug, until that's fixed it might be best to temporarily swap to an in code scheduler
2 years ago
yeah the bot is a little silly at times, show me some form of proof and I'd add the badge for you
thanks, much appreciated. First thing I will try is to run it one minute later, at 1 * * * * and then I will switch to a code scheduler. That's actually how it was implemented before I tried the cron option
2 years ago
if it worked, railway's cron would be better since that means no idle resources
2 years ago
2 years ago
hello everyone, the cron schedule is still buggy? I've seen my cronjobs all skipped since today
2 years ago
I haven't heard of any big improvements so I would assume that yes it's still buggy
2 months ago
Any update on this? Railway CRON scheduler is so unreliable and sometimes it runs the schedule at random times. It costs us thousands of dollar in AI credit due to this unforseen run. Please fix
2 months ago
It doesn't even always start manually
2 months ago
the problem is still relevant