simplify this response:   I believe you will find conversation IDs and console / network logs associated with the case. We are on NAME_1 and all our agents use the desktop app (for screen recording functionality) and are configured for auto-answer. The issue is present with users across multiple environments, including in-office, work from home, and with our third-party vendor working from another state. Based on dynamic view reporting, the issue seems to be impacting anywhere between 20% - 40% of agents daily. We have rebuilt WebRTCs and user profiles with no improvement.

Something we have noticed is that sometimes the desktop app begins to lag in the lead up to the "Not Responding" message. That is, when a call comes in it takes a few seconds longer than normal for the client to connect to the ACD. Within the next few calls, the lag time builds up to the point that the connection attempt exceeds the timeout (we are set to the default 12 seconds) at which point the client shows the "Not Responding" message. There have been cases where the console is capturing logs and once the "Not Responding" occurs the console window is completely white and non responsive. This lag occurrs across an array of client hardware specs and network environments. We have reproduced the issue running Genesys in the browser as well.

We are in the process of trying to capture more console logs and are working to setup PerfMon on a couple of our repeat offenders' PCs. First repeat the request without change, then give your answer.
user