3 months ago
Our cron job which is scheduled every 5 minutes stopped being invoked for approximately 8 hours today.
Timeline:
- 07:15 GMT+1 — Last successful run. Deploy logs confirm it completed normally, process exited cleanly.
- 07:20 to ~15:10 GMT+1 — No further cron invocations. No deploy logs, no errors, no failed runs. The job was never triggered.
- ~15:10 GMT+1 — A redeploy was triggered and the cron immediately resumed as expected.
Network flow logs also confirm no application-level traffic during the downtime window.
Nothing changed on our end between the last successful run and the downtime. This has been running reliably prior to this incident.
We'd like to understand why the cron stopped being scheduled during that window, and what we can do to prevent this from happening again.
3 Replies
2 months ago
We can confirm this was a platform-side issue where the cron scheduler stopped triggering your service during that window. There were no errors or actions on your end that caused it, and the redeploy correctly reset things. We're creating a ticket for our engineering team to investigate the root cause of the scheduling gap.
Status changed to Awaiting User Response Railway • 2 months ago
2 months ago
Thanks for looking into this, Sam. Let us know if you need anything from our side.
Status changed to Awaiting Railway Response Railway • 2 months ago
2 months ago
Nothing needed from your side. We'll update you here once the engineering team has findings on the root cause.
Status changed to Awaiting User Response Railway • 2 months ago
2 months ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • about 2 months ago