Thanks Scott,
Now your 1st message makes totally sense
Jacques
Le 01/05/2018 à 21:53, Scott Gray a écrit :
Hi Jacques,
A job won't even be marked as crashed until the restart. The crashed status
is a record of what happened, done in the same breath as rescheduling the
job. So if you see a
Hi Jacques,
A job won't even be marked as crashed until the restart. The crashed status
is a record of what happened, done in the same breath as rescheduling the
job. So if you see a crashed job in your db, then it has already been dealt
with.
Regards
Scott
On Mon, 30 Apr 2018, 21:55 Jacques Le
Hi Scott, Gil,
If I understand well, OOTB crashed jobs are only restarted at startup. So maybe
adding a link to manually restart them any time makes sense?
Jacques
Le 27/04/2018 à 07:48, Gil Portenseigne a écrit :
Hello Scott,
Thanks for the review and the pointer to reloadCrashedJobs.
I
Hello Scott,
Thanks for the review and the pointer to reloadCrashedJobs.
I decided to add a manual way to reset a crashed job since we met, in one of our
implementation, the issue that the crashed job wasn't rescheduled.
Since only a basic menu was missing to offer a way to reset it, i guess it
Hi Gil,
Maybe I'm missing something but crashed jobs are reset at the same time
that they're marked as crashed (during startup). I don't have the latest
code in front of me but it used to be in JobManager.reloadCrashedJobs().
Basically when an instance restarts, any jobs marked as running are
