action #28714

Updated by EDiGiacinto over 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 Strictly related to #28355, currently we avoid that by not starting which avoids to start working on invalid jobs (but this should not happen in first place). happen).