*knock on wood* I am not seeing this error. Logged in as superadmin, if it makes any difference.

I just for a confirmation that this is a real thing going on….will have a ticket # that yawl can reference shortly….

Superadmins aren’t seeing this, but PUs are. They are working on a fix.

I’m a superadmin and am having the issue. 

Oh boy, now I am too! First thing this AM I wasn’t having this issue, which probably caused confusion for the first chat agent I talked to.

SA reporting the issue...just placed a ticket and they confirmed a fix is in development.

If it helps to refer people to a ticket # 253580.

Thanks for the update as we are experiencing the same issue.

Hi everyone, we are aware of this issue and are actively working to resolve it as quickly as we can.

Please follow this KI post:

Checking on status of this issue. It’s been several hours since first reported. 

@Holly we’re updating the above linked post with updates to this issue.