a64cb229-ac29-4d6b-ab09-c35744abf268

First cron: 57 0-20 * * 1-5

Second cron: 0 * * * 1-5

can you clarify on what you mean by project wide cron timeout?

It just stops at starting container

I have two instances deployed in the project

Both have cron tasks

can you provide a deep link to that deployment

How

copy the url

https://railway.app/project/a64cb229-ac29-4d6b-ab09-c35744abf268/service/b7915fa2-4202-4602-9d76-68a3b8e2389b?id=7f8d0797-2382-43c0-95b4-6f4622f888ea

The first deployment before ‘skipped’ was when it occurred

The first completed after was when I had to manually deploy (then it returned to normal)

It could be relevant that I am running a subprocess within the app that uses ssh -tt

@Brody do you recommend using your cron template

i've looked into the workflow that ran the cron job you have linked and there are no indications that this was a platform issue, from our prospective the deploy went off without an issue.

this means your app itself failed to start.

But two different deployments had the exact same problem. I find that very strange.

your application failed to start twice, unfortunately railway has no more visibility into what your own code is or is not doing than you would.