Struggling to get Lex v2 bot to work with Connect

Question

I have a simple bot that works in the Lex v2 Test interface.  When I hook it up to Connect, having used the correct version and alias and setting the correct language (en-GB) in the "set voice" node, when I initially connect I hear the input prompt but the Error case triggers with a

> { "Results": "Error", ... }

Response in CloudWatch.  Is there a good way to diagnose what's wrong?  I don't see any logs for Lex/Lambda and only get the Connect Flow Logs to go off and they don't give much detail.

Answer

Validate that the Lex bot works independently by testing it on the Lex console. This helps determine if the issue is with the bot itself or the Connect integration.

Some common reasons for integration failures are exceeding resource quotas when associating the bot, issues with IAM permissions for the CLI association, timeouts during the Lex session, or the contact flow taking the error path instead of returning the Lex response.

Ensure the Lex intents are properly identified with the customer inputs in the contact flow. Also check that the Lex alias and language match what is configured in Connect.

Keep it SIMPLE in the beginning...

Answer

In the flow are you setting the correct voice that matches the bot, and setting the 'set language attribute'?

Struggling to get Lex v2 bot to work with Connect

Relevant content