Currently when loading or validating a new config the isself check is run when holding the mutex/lock and it can lead to a dead lock or client/operation delays.

We should instead schedule any long running IO, like the network request isself might make, of any lock.

We may also want to audit the code to make sure no instance of this pattern exist, where we hold the mutex and issue network/disk work.