We are on a fully hosted Genesys Cloud. No local Edges. All hosted by Genesys. We have seen a significant increase in agents changing to "Not Responding" despite the fact that they are on auto-answer. All agents are using WebRTC. We have a case open. But, thought I'd give the heads-up here in case anyone else is having issues.

In looking at one of the agents, her Chrome page starts blocking her microphone between calls. We change the Chrome setting to unblock the Mic and she started working for a while. Later, it stopped routing calls to her, but her mic was not blocked.

At one point today, we had 7 agents with Auto-answer that went into Not Responding status. In talking to them, they said this problem started on Monday.
#Routing(ACD/IVR)

------------------------------
Jeff Gaedke
Goldman Sachs
------------------------------

We are seeing this issue on and off with our on-prem edges. Most often it seems to be related to the home-networking of the affected agents. Rebooting the end-user device, and their internet/wifi gateway, etc. usually addresses those cases.
Every 3 months or so we have seen a larger call routing issue that is fixed only by rebooting our edges. In this case, agents are showing as Available / On Queue, but are not routed calls. The number of affected agents grows over time, so it seems to be some kind of resource issue/leak on the edges. Unfortunately, Genesys support has yet to determine a root cause.

------------------------------
Sven Schiller
Kognitiv
------------------------------

Original Message:
Sent: 05-04-2022 23:57
From: Jeff Gaedke
Subject: Agents switching to Not Responding

We are on a fully hosted Genesys Cloud. No local Edges. All hosted by Genesys. We have seen a significant increase in agents changing to "Not Responding" despite the fact that they are on auto-answer. All agents are using WebRTC. We have a case open. But, thought I'd give the heads-up here in case anyone else is having issues.

In looking at one of the agents, her Chrome page starts blocking her microphone between calls. We change the Chrome setting to unblock the Mic and she started working for a while. Later, it stopped routing calls to her, but her mic was not blocked.

At one point today, we had 7 agents with Auto-answer that went into Not Responding status. In talking to them, they said this problem started on Monday.
#Routing(ACD/IVR)

------------------------------
Jeff Gaedke
Goldman Sachs
------------------------------

We have also seen this (fully hosted Genesys Cloud)

Beyond this specific issue, I noticed there are a lot of instances where phones are Alerting for several seconds before being auto-answered.  This seems to be spread among different reps, not always the same people.   Alert time can range from half a second to 15 seconds (then Not Responding).  This variance causes grief for those trying to answer the phones and inflates the AHT just a little.  We opened a ticket but haven't heard back on it yet, it's frustrating.

------------------------------
Kyle Peterson
Athene
------------------------------

Original Message:
Sent: 05-04-2022 23:57
From: Jeff Gaedke
Subject: Agents switching to Not Responding

We are on a fully hosted Genesys Cloud. No local Edges. All hosted by Genesys. We have seen a significant increase in agents changing to "Not Responding" despite the fact that they are on auto-answer. All agents are using WebRTC. We have a case open. But, thought I'd give the heads-up here in case anyone else is having issues.

In looking at one of the agents, her Chrome page starts blocking her microphone between calls. We change the Chrome setting to unblock the Mic and she started working for a while. Later, it stopped routing calls to her, but her mic was not blocked.

At one point today, we had 7 agents with Auto-answer that went into Not Responding status. In talking to them, they said this problem started on Monday.
#Routing(ACD/IVR)

------------------------------
Jeff Gaedke
Goldman Sachs
------------------------------

Jeff- did you ever get a fix for this issue?

------------------------------
Dawn Weston
AvalonBay Communities, Inc.
------------------------------

Original Message:
Sent: 05-04-2022 23:57
From: Jeff Gaedke
Subject: Agents switching to Not Responding

We are on a fully hosted Genesys Cloud. No local Edges. All hosted by Genesys. We have seen a significant increase in agents changing to "Not Responding" despite the fact that they are on auto-answer. All agents are using WebRTC. We have a case open. But, thought I'd give the heads-up here in case anyone else is having issues.

In looking at one of the agents, her Chrome page starts blocking her microphone between calls. We change the Chrome setting to unblock the Mic and she started working for a while. Later, it stopped routing calls to her, but her mic was not blocked.

At one point today, we had 7 agents with Auto-answer that went into Not Responding status. In talking to them, they said this problem started on Monday.
#Routing(ACD/IVR)

------------------------------
Jeff Gaedke
Goldman Sachs
------------------------------

We have had this happen a lot in the past two weeks as well. Are rebooting Edges what the actual fix is for this?

------------------------------
Kara VanderBeek
Athene
------------------------------

Original Message:
Sent: 01-03-2023 15:06
From: Dawn Weston
Subject: Agents switching to Not Responding

Jeff- did you ever get a fix for this issue?

------------------------------
Dawn Weston
AvalonBay Communities, Inc.

Original Message:
Sent: 05-04-2022 23:57
From: Jeff Gaedke
Subject: Agents switching to Not Responding

We are on a fully hosted Genesys Cloud. No local Edges. All hosted by Genesys. We have seen a significant increase in agents changing to "Not Responding" despite the fact that they are on auto-answer. All agents are using WebRTC. We have a case open. But, thought I'd give the heads-up here in case anyone else is having issues.

In looking at one of the agents, her Chrome page starts blocking her microphone between calls. We change the Chrome setting to unblock the Mic and she started working for a while. Later, it stopped routing calls to her, but her mic was not blocked.

At one point today, we had 7 agents with Auto-answer that went into Not Responding status. In talking to them, they said this problem started on Monday.
#Routing(ACD/IVR)

------------------------------
Jeff Gaedke
Goldman Sachs
------------------------------

We've had this going on since mid December.  We had Genesys clear the cache on our Edges last night but we were told this is a temporary fix.  We have been told "Genesys found a bug that is causing the Edge config cache to not get updated, resulting in station configuration issues."  The next release of the Edge firmware is supposed to have a patch, but there was no ETA given when that might be available.

------------------------------
Brent Bucey
AAA Club Alliance Inc.
------------------------------

Original Message:
Sent: 01-19-2023 16:43
From: Kara VanderBeek
Subject: Agents switching to Not Responding

We have had this happen a lot in the past two weeks as well. Are rebooting Edges what the actual fix is for this?

------------------------------
Kara VanderBeek
Athene

Original Message:
Sent: 01-03-2023 15:06
From: Dawn Weston
Subject: Agents switching to Not Responding

Jeff- did you ever get a fix for this issue?

------------------------------
Dawn Weston
AvalonBay Communities, Inc.

Original Message:
Sent: 05-04-2022 23:57
From: Jeff Gaedke
Subject: Agents switching to Not Responding

We are on a fully hosted Genesys Cloud. No local Edges. All hosted by Genesys. We have seen a significant increase in agents changing to "Not Responding" despite the fact that they are on auto-answer. All agents are using WebRTC. We have a case open. But, thought I'd give the heads-up here in case anyone else is having issues.

In looking at one of the agents, her Chrome page starts blocking her microphone between calls. We change the Chrome setting to unblock the Mic and she started working for a while. Later, it stopped routing calls to her, but her mic was not blocked.

At one point today, we had 7 agents with Auto-answer that went into Not Responding status. In talking to them, they said this problem started on Monday.
#Routing(ACD/IVR)

------------------------------
Jeff Gaedke
Goldman Sachs
------------------------------

We have also seen this occurring on multiple orgs since mid December, it seems to have gotten worse since the beginning of January.  We haven't had any feedback from Genesys.  It is very interesting what you have said about the bug, will ask them about that on one of our cases.

------------------------------
Braiden
------------------------------

Original Message:
Sent: 01-19-2023 19:55
From: Brent Bucey
Subject: Agents switching to Not Responding

We've had this going on since mid December.  We had Genesys clear the cache on our Edges last night but we were told this is a temporary fix.  We have been told "Genesys found a bug that is causing the Edge config cache to not get updated, resulting in station configuration issues."  The next release of the Edge firmware is supposed to have a patch, but there was no ETA given when that might be available.

------------------------------
Brent Bucey
AAA Club Alliance Inc.

Original Message:
Sent: 01-19-2023 16:43
From: Kara VanderBeek
Subject: Agents switching to Not Responding

We have had this happen a lot in the past two weeks as well. Are rebooting Edges what the actual fix is for this?

------------------------------
Kara VanderBeek
Athene

Original Message:
Sent: 01-03-2023 15:06
From: Dawn Weston
Subject: Agents switching to Not Responding

Jeff- did you ever get a fix for this issue?

------------------------------
Dawn Weston
AvalonBay Communities, Inc.

Original Message:
Sent: 05-04-2022 23:57
From: Jeff Gaedke
Subject: Agents switching to Not Responding

We are on a fully hosted Genesys Cloud. No local Edges. All hosted by Genesys. We have seen a significant increase in agents changing to "Not Responding" despite the fact that they are on auto-answer. All agents are using WebRTC. We have a case open. But, thought I'd give the heads-up here in case anyone else is having issues.

In looking at one of the agents, her Chrome page starts blocking her microphone between calls. We change the Chrome setting to unblock the Mic and she started working for a while. Later, it stopped routing calls to her, but her mic was not blocked.

At one point today, we had 7 agents with Auto-answer that went into Not Responding status. In talking to them, they said this problem started on Monday.
#Routing(ACD/IVR)

------------------------------
Jeff Gaedke
Goldman Sachs
------------------------------