When I click "Run now", all it does is another build, which shouildn't be needed.

They're all stuck like this

Not getting any logs out of it either

Cron will not run if there is another running process.
Are you killing your processes? Did one of them never fully complete?

I'm doing sys.exit(0) around the whole program with a try except, I don't see an indication that anything else is actually running.

It started failing at night when I didn't deploy anything

All it's saying is "Ready" and never "Active" like my other serivice that is for sure running.

It did actually say "Deploying" for about 2 seconds before switching to "Ready" hmm

I tried printing something at the very top of my program before anything could possibly crash, and it's not showing up. So I'm inclined to think that the deployment is either not happening or failing silently.

Hmmm, very strange.
Can you try switching to a different builder and if not that, a different runtime?

Would it would to just enable New Builder Environment ? I don't know anything about how to use Nixpacks.

I can try the Legacy runtime though

You can do it all in the settings tab. No need to worry about chaning your nixpacks

This is my CRON service settings.
Not saying you need to match; just worth trying to see if something is going on with one of the settings (builder or deploy)

My thing is based on a dockerfile though

(so is mine)

Switching to the legacy runtime made no difference

? You shouldn't have needed to make a commit for it.

Regardless, that is strange. <:hmmmm:419873765732777984> idk. I wonder if anyone else has any ideas

I used the railway.json thing. Wasn't able to edit it in the UI. It just jumped back.

Trying the New Builder Environment now. It got stuck for a minute at the end, but now I got a "Completed" status at least. No deploy logs though. The details view is not updated either. Going to try "run now"

It's a bit unclear wether the build actually completed or not. Seems like it might not have. Maybe us-west.registry.rlwy.net is responding too slowly?

Yea, I was just about to say that. It looks like it isn't actually building. Very strange.

Yeah failed build even though it has a "Completed" status, and then other stuff happening after gets "confused"?

They keep stacking up like this. With the New Builder Environment it goes to "Completed", without it just gets to "Ready"

0 deployment logs from either of them.

Without New Builder Environment, it does seem to be pushing the image fully though

!t

Here's a timeline in CEST. The cron ran every 10 minutes, then it stopped for some hours, and then it worked once, and then it stopped again.

It started running as expected again