Details
-
Improvement
-
Resolution: Duplicate
-
Minor
-
None
-
None
-
None
Description
Using the safe guards ( in general ) is a very wise thing. However, it is also common for "exceptional events" that exceed the "normal safeguards" to happen. Which leads to the issue of manually disabling and running the jobs again. And possibly affect other jobs, or forces you to spin up a separate JVM to do it in isolation. ( Which may still leave scheduling issues as well.)
I think it would be much better to be able to "flag a job to use alternate failsafe config values" the next time it runs. Then have it "auto revert" to the normal failsafe settings.
This would allow:
the admin to "kick it off now" or just let it "get fixed on the normal schedule"
Not require a separate JVM
Not impact/risk impacting other jobs while the "safe guards are altered".