3 months ago
Before this, I pushed an update to most of my services (relatively in succession),
So at any 1 point in time, there were like 3 builds running concurrently.
For some reason after everything is built and deployed, the cron is just no longer running throghout anymore.
This is NOT the first time I have experienced this, sometimes the cronjobs would just not work, and I would typically fix this by redeploying.
There are NO logs, no crashes, as I have tested this locally and my code works
19 Replies
3 months ago
Project ID
07132e98-0ccf-43b8-aa35-1d32c2fdbcfb
3 months ago
Facing same issue
3 months ago
!e
3 months ago
!t
3 months ago
This thread has been escalated to the Railway team.
Status changed to Awaiting Railway Response angelo-railway • 3 months ago
3 months 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!
3 months ago
Attaching this to an ongoing investigation we have! Will provide an update when we have more information.
Status changed to Awaiting User Response Railway • 3 months ago
3 months ago
Even the 'Run now' button doesnt make the cron job to run
Status changed to Awaiting Railway Response Railway • 3 months ago
3 months ago
This is currently under investigation and unfortunately we do not have an ETA to share yet.
Please note that we do not guarantee cron jobs will be executed on the dot; there may be a slight delay of up to a few minutes from the time it's scheduled to run, including when you invoke it through the "Run now" button. A few minutes of delay is normal, but a delay of more than 10~15 minutes is not.
Status changed to Awaiting User Response Railway • 3 months ago
3 months ago
Its not a minor delay, instead of running every 5 minutes, its not running for more than 3 hours now. Is that sounds reasonable to you?
Status changed to Awaiting Railway Response Railway • 3 months ago
3 months ago
I understand and agree that is not a minor delay in the slightest. Wanted to reinform that slight drift is to be expected but that level is not ideal.
As I had said previously, we currently are investigating the cause of this and working towards a fix. I do not have a set ETA on when that will be out. I appreciate your patience with this!
Status changed to Awaiting User Response Railway • 3 months ago
3 months ago
looks like this is a bigger issue outside yes? I mean I am in a hobby plan for a reason, and this is to be expected :)
3 months ago
I don't think that's a valid assumption to make for any plan. It's a cron job, it should be cronning.
3 months ago
No what I mean is like I do not expect it to run at like the very dot. A drift of a couple of minutes is ok, but of course if you set the Cron at x time and it appears to run x + 2 hours, then something is indeed wrong
3 months ago
And I believe Railway prioritizes cron timeliness for the higher tiers no?
3 months ago
When we have to start several thousand cron jobs every 5 minutes, there will be some inevitable drift, but we have set up monitoring for missed runs and will be looking into what we can do to prevent that.
3 months ago
<:salute:1137099685417451530>
3 months ago
🛠️ The ticket Scheduling Inaccuracy Issue has been marked as in progress.
3 months ago
Update here: we have made significant changes here, and the cron job delay is now down to 22 seconds on average.
3 months ago
✅ The ticket Scheduling Inaccuracy Issue has been marked as completed.
Status changed to Solved brody • 3 months ago