Skip to content

VOICEID on Amazon connect. Error in AgentAppService.VoiceId.describeSpeaker

0

I have activated Voice ID following the steps in this tutorial. [https://catalog.us-east-1.prod.workshops.aws/workshops/ed3fc8e1-cb23-4bce-b2f3-a2bfeaa3aa7d/en-US/1enabling-amazon-connect-voice-id]. The flow is working correctly, indicating that the user is not registered with Voice ID and is passed to the agent. However, when the contact is opened in the agent and the client is registered, a loading icon appears and the message "Voice sampling." After a while, a timeout message appears. Reviewing the logs, I see the following log. I have checked the permissions, the security profile has access to Voice ID marked, and in the analysis in the searches as well. The domain is also configured correctly in the instance. What could this be?

{ "component": "ccp", "level": "ERROR", "text": "'AgentAppService.VoiceId.describeSpeaker' API request failed", "time": "2025-03-27T22:03:51.126Z", "tabId": null, "exception": { "type": "[object Object]", "message": "Bad Request", "stack": [] }, "objects": [ { "request": { "event": "api_request", "requestId": "1743113030874-o57py2f0bcs", "method": "AgentAppService.VoiceId.describeSpeaker", "params": { "SpeakerId": "[obfuscated value] 4fc9f66fb6b296af709ae56f8e379d64", "DomainId": "SaMsSRaMSq6chOjVc0ZYsy" } }, "response": { "event": "api_response", "requestId": "1743113030874-o57py2f0bcs", "err": "{"message":"Bad Request","status":400}" } } ], "line": 286, "agentResourceId": "b62243f8-d019-443d-9a5d-9ec242e9ce6d", "loggerId": "1743112948955-epcxcyg9o7p", "contextLayer": "SharedWorker" }

asked 2 years ago188 views

1 Answer
0

I ran into something similar recently. The Bad Request from AgentAppService.VoiceId.describeSpeaker usually points to a mismatch or missing field in the SpeakerId or DomainId being passed.

Make sure you're not accidentally passing the full ARN or including extra characters/spaces. I once had an issue where the ID had a trailing space after being pulled from an attribute in the flow.

Voice ID domains are region-specific. If your Contact Flow and the Agent App are pulling from different regions (or using stale DomainId references), it might throw that 400 error. There's a subtle race condition where the agent app might try to describeSpeaker before the enrollment is fully completed. You can work around this by introducing a small wait or re-check before triggering that call. Sounds silly, but I’ve seen the CCP hang on stale JS resources, try hard-refreshing the CCP or open it in an incognito tab.

answered a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.