a year ago
I have a cron schedule set up to run daily at 1am UTC 0 1 * * * which hasn't fired for the last 4-5 days, and before that it's been triggering like half the time.
The UI correctly states the service should run at 01:00 AM, and I have a deployment ready that I can run manually through the Railway UI with no issues, so I am unsure what else could be preventing the cron job from triggering.
Am I doing anything wrong?
Project: 8afc855c-4a51-4281-9a70-64918d09f672
Service: e3554c96-0934-45d0-aae3-fcfa1ba7c6d1
5 Replies
a year ago
Yes. It always completes in under 2h, sometimes much faster.
a year ago
Then there's likely too many jobs running at 1am UTC and yours is being skipped by their scheduler, they do have plans to improve this but until then I would have to recommend you switch to an in-code cron scheduler.
a year ago
Nice! Good tip. I have tested 7am and 7:25am UTC and it has fired correctly.
Do you have data on the distribution of schedules by any chance? Or any advice? I need my cron job to trigger around 1-3am UTC but not later than that. I'm thinking whether a time like 1:30am or 1:45am would be reliable or do I need to space it out more?
a year ago
Midnight UTC was over scheduled, and then everyone was asked to try 1am UTC, so 1:30am / 1:45am would definitely be better, but if you need absolute reliability, for the time being I would still recommend an in-code scheduler.