Hi Tom,
We have seen similar behavior occasionally, especially when Co-Pilot is open alongside heavier admin workflows such as:
- OAuth configuration
- SCIM provisioning setup
- Admin pages with many dynamic components
- long-running API/UI requests
From what we observed, it does not necessarily look like a SCIM-specific issue, but more like a browser/UI resource contention scenario between the embedded Co-Pilot experience and certain Genesys Cloud admin pages.
A few things that helped during troubleshooting:
- testing in an incognito/private session
- disabling browser extensions temporarily
- testing another browser profile
- checking browser console logs/dev tools for UI errors
- validating if the issue happens only when Co-Pilot is docked/open
- monitoring memory/CPU spikes in the browser tab
We also noticed the behavior tends to appear more frequently when:
- multiple admin tabs are open
- the org has many active integrations/extensions
- long conversations/history are kept in the Co-Pilot pane
- the browser session has been active for a long time
One thing worth mentioning from the Copilot architecture side:
Genesys Cloud Copilot heavily relies on contextual UI rendering and live interaction with Knowledge/AI services, so some admin pages with complex frontend rendering can occasionally become less responsive depending on browser state and client-side resources.
I would probably recommend gathering:
- browser console logs
- HAR/network trace
- timestamp/session details
and opening a Genesys Care case if the freezing is reproducible consistently.
The console logs article is useful here:
Gather Console Logs
And the Copilot overview:
About Genesys Cloud Copilot
So far, I would not consider this expected behavior, especially if the UI becomes completely non-interactive without refresh.
------------------------------
Gabriel Garcia
NA
------------------------------