action #28714

Updated by EDiGiacinto about 2 years ago

It seems that under certain conditions (possibly websocket connection turned down) the worker sets the job to an invalid value.

Logs of that happening can be seen in #28355, currently we avoid that by not starting on invalid jobs (but this should not happen in first place - as the job will go from assigned back to scheduled - and can cause problems, e.g. wrt MM clusters).


- Investigate, verify that it still happen and fix it properly as #28355 is a workaround