Known Issues and Non Supported Features
nThe details below outline the list of Know Issues and Non-Supported Features. Customers wishing to make use of such features, are requested to raise a Feature Request through their TAM or Custom Success Manager.
Issue | Cause | Workaround |
|---|---|---|
When a conferencing a second Agent into an existing call via the Directory, the second agent is able to end the call with the customer when they hang up on the call. | When AWS released the Enhanced calling and monitoring capabilities functionality, the feature includes changes to the agent call experience behaviour.
| Disable support for Enhanced calling and monitoring capabilities until the feature is supported within Agent Desktop  |
New issues have started occuring such as error messages, failures to mute, or hear incorrect ringtones | Google Chrome Changes to Storage Partitioning. AWS advised: Some of your agents using the Amazon Connect Contact Control Panel (CCP) may be impacted by an upcoming change to the Google Chrome browser. Google will begin deploying a change to introduce storage partitioning [1] to the Chrome browser on July 25, 2023 to 1% of users. Agents that have this Chrome change applied and that use the CCP in multiple distinct applications (such as embedded in two different CRMs) may experience error messages, failures to mute, or hear incorrect ringtones. Calls will still be connected to agents as expected. If you have developed a custom integration using the streams.js library to embed the CCP into your own application, you may also see spurious error events in this situation. We are working on a change to the Connect CCP and streams.js library to properly handle these events." | No current work around for Google Chrome. Pending AWS working on a change to Connect Streams. Customers may wish to use Firefox or Edge Chromium browsers until the update is made |