A growing number of our users have started, at random, to encounter the issue captured in the attached screenshot. Clearing teams' cache files seem to resolve the issue. Tracing using Fiddler or WireShark is very difficult as it would need to be started before the issue occurs, while not knowing when / where the issue will occur. What can we do to understand where the culprit of this issue lies ? We have a support request opened, but it's halted to a crawl because they need us to provide logs (that we can't provide) before they can help us, and since we are unable to comply, they most likely won't be able to assist. Can anything be done to better understand what is causing this, either being the service or something else ?