Topic by Jared
We're seeing an intermittent issue with the 3PQ Chat Routed method. We are very definitely using only a single client to the 3PQ API server. We send all chat pop requests from the clients to this single server, yet are seeing the same issue which was happening with multiple endpoints connected to the server.
We make the ChatRouted call, receive SUCCESS, relay that message to the agent desktop. Consistently, we can do this dozens and dozens of times, with SUCCESS every time. However, every now and then, with nothing different happening with the agent or server side, the chat simply doesn't pop into the agent workspace.
We made a non-trivial architecture change to meet the requirement of using a single client to the API, and continue to see the same issue. There are no logs for this because the logs show successful screenpops, but if needed we can reproduce it and provide ChatIds for items which did not populate. Are there any logs we have access to which will give more information on this?
Please advise,
-Jared
