Cron stuck in limbo
Anonymous
PROOP

a year 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…".

28 Replies

Anonymous
PROOP

a year ago

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


a year ago

can you try switching back to the previous cron UI?


Anonymous
PROOP

a year ago

where at?


Anonymous
PROOP

a year ago

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


a year ago

service settings


Anonymous
PROOP

a year ago

done


Anonymous
PROOP

a year ago

is there another step then?


a year ago

refresh your broweser


Anonymous
PROOP

a year ago

still seems to be stuck in limbo


Anonymous
PROOP

a year ago

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


a year ago

screenshot please


Anonymous
PROOP

a year ago

How it looks in new cron ui


Anonymous
PROOP

a year ago

1287500711344603100


Anonymous
PROOP

a year ago

Even though I have

1287500872011747300


a year ago

thats not limbo, it just wont stop running


Anonymous
PROOP

a year ago

feels like limbo to me

1287502188935118800


Anonymous
PROOP

a year ago

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


a year ago

does your code do a clean exit() ?


Anonymous
PROOP

a year ago

it does now <:blobyes:1149662717213417565>


Anonymous
PROOP

a year ago

but that one probably not


Anonymous
PROOP

a year ago

which is what I was trying to fix


a year ago

okay let me try something


Anonymous
PROOP

a year ago

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

1287502988180455400


Anonymous
PROOP

a year ago

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


a year 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

a year ago

seems to have done the job


Anonymous
PROOP

a year ago

thx for the help advice 😉


a year ago

no problem!


Loading...