Cron never getting to "completed" state
Project id: ec89ba1e-1366-4f12-af35-f0c3f8bd3ef6
I have a cron that stopped running a few hours ago. Now it's only ever "building" or in the "ready" state, never "completed".
29 Replies
Project ID:
ec89ba1e-1366-4f12-af35-f0c3f8bd3ef6When 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 thoughYou 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
