(Created page with "=Troubleshooting Workspace Web Edition= If you are having issues with Workspace Web Edition, you can try some of these solutions. ==Slow search results== For agents using I...") |
|||
| Line 5: | Line 5: | ||
==Slow search results== | ==Slow search results== | ||
| − | For agents using Internet Explorer 11 who are experiencing slowness in the display of search results and of Favorites in Team Communicator, set the value of the '''teamcommunicator.enable-lazy-loading''' option to true to enable a lazy loading mechanism, allowing agents to get acceptable display performance. | + | For agents using Internet Explorer 11 who are experiencing slowness in the display of search results and of Favorites in Team Communicator, set the value of the '''teamcommunicator.enable-lazy-loading''' option to <tt>true</tt> to enable a lazy loading mechanism, allowing agents to get acceptable display performance. |
| + | |||
| + | ==CPU overload== | ||
| + | |||
| + | Search the agent Browser logs for the term "performance problems" to confirm whether performance issues that an agent might be experiencing are related to CPU overload. | ||
| + | |||
| + | ==Network issues== | ||
| + | |||
| + | You can review logs to determine whether agents are experiencing network issues by searching for Ajax command names followed by the time. In general, commands should take less than 1 second. | ||
| + | |||
| + | Search for "<tt>Command: '<command name>' sent in <time></tt>" | ||
| + | |||
| + | For example: <tt>Command: 'Hold' sent in 0.337s</tt> | ||
[[Category:V:HTCC:9.0.0DRAFT]] | [[Category:V:HTCC:9.0.0DRAFT]] | ||
Revision as of 16:07, February 3, 2021
Contents
Troubleshooting Workspace Web Edition
If you are having issues with Workspace Web Edition, you can try some of these solutions.
Slow search results
For agents using Internet Explorer 11 who are experiencing slowness in the display of search results and of Favorites in Team Communicator, set the value of the teamcommunicator.enable-lazy-loading option to true to enable a lazy loading mechanism, allowing agents to get acceptable display performance.
CPU overload
Search the agent Browser logs for the term "performance problems" to confirm whether performance issues that an agent might be experiencing are related to CPU overload.
Network issues
You can review logs to determine whether agents are experiencing network issues by searching for Ajax command names followed by the time. In general, commands should take less than 1 second.
Search for "Command: '<command name>' sent in <time>"
For example: Command: 'Hold' sent in 0.337s