The update timestamp isn't updated when a run successfully finds nothing to mirror. The "No completed run" warning only happens when lock contention is seen. So if the first update after a long period of no updates takes long enough, warnings will be spewed even though there's really no problem.

Seems obvious that the timestamp should be updated after every successful check even if there's nothing to mirror.