cron runs fine, rare but inconvenient bug
4 hours ago I had a project wide cron timeout, which prevented further deploys since (I had to deploy manually). How can I fix this without having to doing an intracontainer cron?
Solution:Jump to solution
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....
14 Replies
Project ID:
a64cb229-ac29-4d6b-ab09-c35744abf268a64cb229-ac29-4d6b-ab09-c35744abf268
First cron:
57 0-20 * * 1-5
Second cron: 0 * * * 1-5can 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
Railway
Railway
Railway is an infrastructure platform where you can provision infrastructure, develop with that infrastructure locally, and then deploy to the cloud.
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 templateSolution
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.