Here are the results from one of my systems:   Date Agents 50002dedups_Hours_% Logins HoursLoggedIn 50002_dedup 50002s 10/22/2018 641 0.069073783 640 5096 352 416 10/23/2018 634 0.06993007 633 5005 350 439 10/24/2018 623 0.07115869 619 4764 339 438 10/25/2018 598 0.067743383 595 4458 302 382 10/26/2018 570 0.09506705 569 4176 397 463 10/27/2018 218 0.100123609 216 1618 162 180 10/28/2018 77 0.075645756 75 542 41 44 10/29/2018 627 0.05625879 627 4977 280 328 10/30/2018 621 0.055180871 619 4893 270 345 10/31/2018 613 0.065718947 611 4291 282 356 11/1/2018 583 0.051089759 580 4267 218 249 11/2/2018 547 0.047793221 545 4101 196 223 11/3/2018 211 0.038961039 210 1540 60 77 11/4/2018 75 0.033149171 74 543 18 18 11/5/2018 595 0.087250712 592 2808 245 262 ... View more

I am not a partner but a customer. However I have recently opened my second TAC case for this very issue. During the first, I engaged the network team who applied a QOS policy to prioritize the Finesse traffic between the call centers and the DC's. At the time we thought the problem was solved. Unfortunately one of our centers recently complained about this issue and I had to open Pandora's box again. I ran a similar query against our Aceyus DB event detail table and grabbed all of the 50002 events by call center, along with the durations. I totaled over six thousand hours of lost productivity due to the random  not ready issue. I have engaged my Cisco team to hopefully work with the BU and TAC on this because I feel like it might be a major issue that is just being swept under the rug... ... View more

We are having what sounds like the same issue, running Finesse 11 with no custom gadgets. Have any of you had success with TAC for this issue? ... View more

I have resolved this myself. The issue was with the location of the code in the desktop layout. I moved it as follows: ... View more