Project id 9bc43410-5b99-4bfa-8b24-9598bb1e0276 Deployment id ecb36898-b8d9-4ad6-a1db-a0963fbad496

This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.

Hey, just wondering how you have determined that it both finished and exited?

Because even when having an uncaught error it will not stop and that made me think of this, but if this isn't enough, we also created a dummy repo with only a python script that prints hello world :))) https://github.com/cbalanean14/DummyPythonScript and ran it and it doesn't exit

and beware of the fact that the app worked for 3 months with no problems with cron jobs every 30 min and we didn't change anything deployment id: ada4c68f-3bbe-4b71-9922-3bd6e99eb5d0

Maybe it's an issue with the fact that railway still sees the container as active i don't know maybe it exits maybe not but what we know is that it;'s marked as active and future crons are skipped

Could you please attach some screenshots of that repo running as a cron job?

sure, now I see that new jobs aren't marked as skipped either weird, cron is every minute

You can not run jobs every minute.

I run them every 30 min it was an example for testing purposes what is the min amount that you want me to test I will do it

ok 15 min then it will be will respond once i test

I think it's 5 minutes for Hobby users.

This is very weird now it works hmm maybe it's a github web hook issue I don't understand because when updating the service to fix an error the cron job wouldn't run anymore I don't know something happened but now that I messed up with removing the github deployment and resetting the cron job somehow it works again very weird

Anyway thanks maybe there is a bug maybe there isn't but now it works :))

Awesome, in the future, please do not open private posts unless you need to share sensitive information with the team.