A deadlock has been observed between The OldDataMonitor and an AuthorizationStrategy.

When a job has a new build it will call save which will trigger the OldDataMonitor via the SaveableListener.
This will call referTo which in the case of a Run will lookup the parent Job via it's full name. This will perform a permission check .

Now if the authorization strategy is also being saved at the same time then it is highly likely that a deadlock will occur.