...
When the disconnects are happening, it is always good to temporarily disable the software and see if it helped. If that does not yield desirable results, please, click here follow the basic steps from the article.
...
Browser developer tools - the Console section:
...
Please, click here for help.
NO_BROWSER_PING
The NO_BROWSER_PING issue occurs when the XTM application cannot ping the browser anymore, which leads to the WebSockets disconnection. This is rather a user-end issue, and the connection between the browser and XTM Workbench can be blocked by, for example, some software.
...
In most cases, WebSockets issues occurring on the user-end and the XTM support team is often unable to directly solve such issues. However, sometimes the problems only seem to lie on the users' end, but it eventually turns out that this is an XTM issue and we need to make some changes. Irrespective on throot of root cause, please, do not hesitate to reach out to the XTM support team with all the above-mentioned information gathered up.