If this hasn't gone to Quest Support, then I'm with you, in that my best guess would be that latency is causing this issue, and possibly the cause for your other issue that you describe in another post, especially since you mention that it's all been happening since you moved to Office365.
I'm guessing that network responsiveness between your org (your workstation) and Office 365 servers is not nearly as consistent as when Office was installed on your workstation locally.
I would open up a Support ticket any way with Quest, to see if any of the Support engineers have seen other customers with this experience. Even if not, Quest can document this issue/condition and the dev teams can do some diligence to see if there is a solution.