3 Antworten
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
0
Yes it turns out that the issue is with ServiceNow.
The Advanced Work Assignment feature in ServiceNow was setting agent availability to Offline based on inactivity in chat queues.
Its a known issue in SN (well, known to support). So I have a workaround for it.
beantwortet vor 3 Jahren
0
Have you run the AWS Connectivity tool to see of the response times and any latency?
https://s3.amazonaws.com/connectivitytest/checkConnectivity.html
beantwortet vor 3 Jahren
0
Have you ran stock CCP and see if the issue happens without SNOW being involved?
david
beantwortet vor 3 Jahren
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor einem Jahr
Hi PaulC-MH, we are experiencing the same issue as you described. Can you share the workaround suggested to you by ServiceNow please?