A fresh job start creates a JobInstance first, and that creation is protected by the SERIALIZABLE + JOB_INST_UN constraint, so only one thread/process wins. However, the restart path does not seem to be protected by that constraint.

This issue is to analyse that and see if this is a valid problem.