Hi Sam 👋, and no worries about posting here and there — in this case posting there is helpful feedback and this is a great place to get help with your specific needs!

Could you confirm if you're still having the issue? We were having an outage earlier and want to make sure that wasn't interfering with your crons not running.

Could you also let me know if this is a recent issue on crons that were previously working as expect, or if it's the first time you tried crons on Railway and ran into this issue?

Hi Chandrika - I'm still having the issue. I just changed the cron schedule to be a couple of minutes ago and the same thing happened (well, didn't happen!). I was initially trying around 18-20 hours ago as well.

I've never had cron working, this is the first time I've tried cron on Railway.

We merged in a fix that should help with this issue! (..and you should be able to try it out with "Run now" too)

I am getting this issue as well. https://www.loom.com/share/7cbb62ce791444cca79d875bb6f8063a?sid=2c42f71d-bb33-4b77-924b-29f47a40d2d2

Hey Clint. Could you try toggling on the "new cron experience" feature flag and seeing if it fires?

Actually Clint it looks like you're already using the new feature flag. So the run should show up under the "Schedule" tab now

Can you confirm it's running there?

It started workign correctly when I turned the feature flag off.

Yea so, it actually was running before it would have just been under that "Schedule" tab (you can see it in your loom)

The new experience has it's own tab for cron stuff because, as you and many users found out, it's really confusing to have Ready, completed, building, deploying, etc all in one place

No, it was NOT executing the startCommand even though it said it was running. I explain that in my video.

Turning off the new front functionality fixed the problem. Now the startCommand gets executed on the cron schedule.

Gotchya. If you could toggle the flag back on and screenshot that "Schedule"/"Cron runs" tab that would be great

Turned it on. It had all the runs from when I had it set to every 5 minutes to test it. None of those actually ran the startCommand. The top one at 8:00 is from me clicking run now just before I recorded, which doesn’t run the command successfully.

I switched the flag back off so my cron will run correctly for now. I won’t be at my computer for a couple days.

Now it’s stuck on the new cron service and I can’t turn it off (feature flag is missing) and it’s not working. Can I get the old version back? It worked. If not I’ll need to switch services asap

Hey clint can you link to the service that's not working?

Is it this service?

https://railway.app/project/02d33f97-7f48-4e35-ab83-c46bc286b00c/service/4948b4c9-80a1-477b-baa4-31dd502031c7/schedule

It looks like your application is still running. When your cron finishes, are you calling "Exit" because if you don't, it'll keep running

You can see in this tab that it's skipped because the instance is still running, and that's what we see when I inspect the instance on our side

Just an FYI there is now an option to enable "Old cron experience" if this is still problematic