- Newest
- Most votes
- Most comments
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
Relevant content
asked 3 years ago
asked 2 years ago
asked 2 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 4 years ago
