10 months ago
- Date of delayed execution: November 20
- Delay duration: ~1 hour
- Cron configuration was unchanged
- No deployments or configuration updates around that time
- Logs suggest the cron trigger itself was delayed, not the job startup inside the container
Are there any known scheduler delays, misfires, or worker-capacity issues around November 20 that could explain a one-hour drift?
Or is it expected or common for cron jobs on Railway to occasionally run later than scheduled?
Thank you :)
2 Replies
10 months ago
Cron Jobs were acting a bit erratically in some cases, so the team implemented some fixes on November 28.
You can read more about it here: https://railway.com/changelog/2025-11-28-buckets-ga#fixes-and-improvements
And if you're still having issues with cron, please let us know so we can forward it to the team!
medim
Cron Jobs were acting a bit erratically in some cases, so the team implemented some fixes on November 28. You can read more about it here: <https://railway.com/changelog/2025-11-28-buckets-ga#fixes-and-improvements> And if you're still having issues with cron, please let us know so we can forward it to the team!
10 months ago
Thank you so much for your reply! It is so cool that the issue was already fixed!
Status changed to Solved medim • 10 months ago