The new locking primitives in 5.2 around jobs assume the worker/scheduler was actually started, so don't try to stop if not started.
The new locking primitives in 5.2 around jobs assume the worker/scheduler was actually started, so don't try to stop if not started.