Known Issues
Issue | Workaround |
|---|---|
We cannot see the new TPEv2 Voice Object since v2.5 release and I can see errors in the browser console log like the below.  The issue does not occur for Zendesk Administrators. | This issue has been triaged as a Zendesk Permission issue. Zendesk is currently investigating. If you have this issue, please raise a Support case with Zendesk Support and advise them you are using the Amazon Connect for Zendesk connector which is using the TPEv2 call object and your agents are having permission errors. We are currently waiting an update from the Zendesk product team on this item. |
Contact Attribute fields which used to show in the Ticket Comment are no longer appearing since the v2.5 upgrade. Some customers have reported these values were used to trigger workflow forms. | As part of the update to TPEv2 from Zendesk, some contact centre data objects are now captured in the new Voice Call object. To have Attribute show in the old yellow ticket comment object, you can set a User defined Contact Attribute in your Amazon Connect contact flows. For example if you used to use You would add a “Set Contact Attribute” block your contact flow with a different value such as Example call flow objects.  |
I have changed my Amazon Connect domain name as outlined by AWS and now I cannot access call recordings from before this date | Call Recording URLs were contructed using the Amazon Connect URL. As these were written to the ticket, after this change, users would have to change the URL when trying to open the link. Please change the domain name section of the URL that opens and try.
Change to:
We are unable to reprocess call recordings that had already been saved in ZD tickets. |
AWS Issued notification - July 2023. "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." | We are currently waiting for the latest Streams .js to be released by AWS so we can upgrade the Application. Whilst we do not know all the issues that can be caused by Google’s change, we are suggesting that customers turn off Auto Update to their browsers to try limit any impact. |