Cron stuck in limbo
Anonymous
PROOP

2 years ago

Not entirely sure whats happening. I noticed a failing cron has been running most the weekend so I deployed a new version with a fix to make sure it times out and exits. Now it just seems stuck with "Running..." and "Build › Publishing image..." with all the following jobs stuck at "Previous job still running...".

Closed

28 Replies

Anonymous
PROOP

2 years ago

4d0e9a9f-22a2-4f52-936b-c9b94fc12e5a


2 years ago

can you try switching back to the previous cron UI?


Anonymous
PROOP

2 years ago

where at?


Anonymous
PROOP

2 years ago

not sure I ever had the previous, only started with the cron on friday


2 years ago

service settings


Anonymous
PROOP

2 years ago

done


Anonymous
PROOP

2 years ago

is there another step then?


2 years ago

refresh your broweser


Anonymous
PROOP

2 years ago

still seems to be stuck in limbo


Anonymous
PROOP

2 years ago

or I dont know, it keeps switching back to new cron ui where its limbo 🤦‍♂️


2 years ago

screenshot please


Anonymous
PROOP

2 years ago

How it looks in new cron ui


Anonymous
PROOP

2 years ago

1287500711344603146


Anonymous
PROOP

2 years ago

Even though I have

1287500872011747379


2 years ago

thats not limbo, it just wont stop running


Anonymous
PROOP

2 years ago

feels like limbo to me

1287502188935118918


Anonymous
PROOP

2 years ago

it completed successfully yesterday, I have removed it and it even state stopping container


2 years ago

does your code do a clean exit() ?


Anonymous
PROOP

2 years ago

it does now <:blobyes:1149662717213417565>


Anonymous
PROOP

2 years ago

but that one probably not


Anonymous
PROOP

2 years ago

which is what I was trying to fix


2 years ago

okay let me try something


Anonymous
PROOP

2 years ago

I have added a promise race where one promise is just a 1 minute timeout

1287502988180455489


Anonymous
PROOP

2 years ago

If I have to I can just nuke the service and re-add but I thought I would flag that something seems off


2 years ago

yeah im pretty sure this was fixed going forward but it wouldnt have fixed it for previous runs, i recommend right clicking on your service and duplicating it


Anonymous
PROOP

2 years ago

seems to have done the job


Anonymous
PROOP

2 years ago

thx for the help advice 😉


2 years ago

no problem!


Welcome!

Sign in to your Railway account to join the conversation.

Loading...