Deno•13mo ago

Cron job still "Executing" while it's Failed since +24h

Hello, my cron job on Deno Deploy is still at "Executing" state while it is actually Failed since more than 24 hours. I tried to :

commit a change to reset cron
commit with changing cron schedule
commit without cron (it got removed from Dashboard but after I reverted it got back to its previous state "Executing" while Failed)
without success.

Any idea?

RayhanOP•12/3/24, 5:46 PM

Changing unique name "resolved" this issue but it seems like process is still not close somewhere because I reverted my unique name change to previous one "Cron job" and it got back to "Executing" Failed state. It should have called somewhere but this is called only signal.abort as the code states here: https://fossies.org/linux/www/deno-2.1.2.tar.gz/deno-2.1.2/ext/cron/01_cron.ts?m=t (search )

Also docs is wrong: https://docs.deno.com/deploy/kv/manual/cron/#retrying-failed-runs
It says that (options) should be in last arg but code says that it should be third if an handler is present. Basically it should be:

see: https://fossies.org/linux/www/deno-2.1.2.tar.gz/deno-2.1.2/ext/cron/01_cron.ts?m=t (search )