a month ago
Hi,
I’m currently using Railway’s scheduled cron jobs, and most of the time they run correctly. However, I’ve noticed an intermittent issue where the cron job does not start at the scheduled time at all, and I have to manually trigger it from the dashboard.
Here’s what I’m seeing:
The schedule is set and saved correctly.
Recent executions show that some days the cron job runs on time, but on certain days it simply doesn’t start.
No logs are generated on the days it fails to trigger.
When I click “Run now,” the job executes normally.
This looks like the scheduler occasionally skips the run entirely.
Could you check why the job is being skipped on some days?
If there are known limitations, delays, or conditions that might prevent cron triggers from firing, please let me know.
I can provide additional logs or screenshots if needed.
Thank you.
8 Replies
a month ago
Hey there! We've found the following might help you get unblocked faster:
If you find the answer from one of these, please let us know by solving the thread!
Railway
Hey there! We've found the following might help you get unblocked faster: - [🧵 Define Instance](https://station.railway.com/questions/define-instance-034d7513) - [🧵 Support configuring multiple cron jobs on same deploy/service](https://station.railway.com/community/support-configuring-multiple-cron-jobs-o-e7f58b23) - [🧵 Cron Job Function not working](https://station.railway.com/questions/cron-job-function-not-working-ba32fe59) If you find the answer from one of these, please let us know by solving the thread!
a month ago
It seems that none of these cases apply to my situation.
a month ago
Hello!
We're acknowledging your issue and attaching a ticket to this thread.
We don't have an ETA for it, but, our engineering team will take a look and you will be updated as we update the ticket.
Please reply to this thread if you have any questions!
24 days ago
Bit of an update, we are still investigating this and a few other issues related to crons. Will provide an update when we have more info!
Status changed to Awaiting User Response Railway • 24 days ago
Status changed to Awaiting Railway Response Railway • 23 days ago
18 days ago
Hello,
An update: We have made several changes to our CRON scheduling system, and from our internal metrics, we have seen this make a massive improvement in CRON execution delay and have eliminated missed CRONs. Additionally, the Run Now button starts the job much faster.
But please let us know if this isn't the case for you!
Best,
Brody
18 days ago
🛠️ The ticket Scheduling Inaccuracy Issue has been marked as in progress.
16 days ago
✅ The ticket Scheduling Inaccuracy Issue has been marked as completed.