Our most recent occurrence of a skipped cronjob was Sunday (July 21, 24), 2 missed cron jobs out of 6 that were set that day. Yesterday and today have been stable.

Yup we noticed a dip in cron activity on Sunday, and have applied a fix as of about 2 hours ago. Please keep us informed!

Didn't notice skips but I had issues with cron reliability in that they would work perfectly for a while and then start running at random times or e.g. 100 times in a row.

Looking through log history this hasn't happened in the last 3 months now and they've been running pretty reliably - albeit I only have one a day now since I moved my business-critical crons to another place.

Glad to be seeing reliability improvements! :)

Keep us posted! Here to support any usecase especially the business critical ones :D

Scheduling for my project has been very unreliable to this day. I try to make a Python script run every 15 minutes. Additionally, this script checks if the time is within working hours and then executes, if not it logs "Not within working hours, exiting script" and finishes executing. For hours this script doesn't execute. It randomly does some times.
I'm appending 2 screenshots of the project and the logs, within 1 hour this script only executed once - when explicitly made it run using Railway UI

Edited: moved to the proper thread

How can I support the bot?

My crons stoped running 5 days ago. Haven't change any code or config in that time. When I click "Run now" it just triggers new build, but doesn't run the start command. Panel shows that next run is scheduled, but when time comes start command is not called. I see only "Ready" states, nothing is "Active".

Did the cron run logic change or something?

Moved couple production crons today, just to find that they are not working

Also, it will be great to have "Cron:Completed" or "Cron:Error" states for all cron runs in history, since now it shows "Removed" and it's pretty strange name.

I'm having a similar issue to @nikitattt - I've tried creating a database backup cron and it only ever gets into a "Ready" state - i.e. built but not deployed. If I deploy as a service without cron it runs successfully and exits when I push, so I think the service is set up correctly. When I push an update or click "Run now" I get another build that sits in a "READY" state, but doesn't run.

Hey y'all. We've rolled out a new cron experience. If you're having issues with the old one, can you enable the feature flag at the bottom of the service settings and report back?

This new cron experience has another tab called "Cron runs" because we found users were very confused by the previous experience of having it all on the deployments panel (ready, deploying, completed, etc states)

8 months since this ticket, and after our quality sprint here, I think it’s safe to say that we delivered here. Going to mark this as completed.