I can't get AWS Connect to work with multiple Lex V2 bots.

Question

I created an AWS Connect flow that works great with the first bot, but I wanted to create a separate bot to provide a different style of anwsers. For testing purposes, both bots were built identical with the same intents, same lambda functions, same utterances, etc. I have triple checked and both are identical.  I have tried rebuilding the 2nd bot and it still doesn't work.

The contact flow has a "get customer input block" where it uses DTMF options 1 and 2.  If I select option 1 everything works. If I select option 2 it's like the bot is not listening to anything I am saying. Cloudwatch says "Results": "Error" for the "get user input" block and it's identical to the option 1 except it points to the 2nd bot.

I have built the bot and tested it in the console and that works fine and I am getting expected responses so I know the 2nd bot works.

Cloudwatch is producing an error as if there was no utterance and the lambda function is getting triggered, but print(event) is not showing an utterance either.

Any ideas? Is there a bug with AWS Connect and multiple Lex V2 bots?

Answer

Since the bot is working fine from the Lex console, sounds like it more of an issue with the link up to Amazon Connect.  Have you checked that it is calling the correct bot/alias from Connect CloudWatch Logs?  In the log where you are getting an error on GetCustomerInput block, there is more details around the bot it is using, such as below.  Make sure it is calling the correct botID/aliasID.
```
"Parameters": {
        "NoInputTimeout": "3000",
        "TextToSpeechType": "text",
        "LexVersion": "V2",
        "BotAliasArn": "arn:aws:lex:us-west-2:xxxxxxxxxxxx:bot-alias/XXXXXXXXXX/ALIASID",
        "Parameter": "",
        "Text": "How can I help you?",
        "Voice": "Matthew",
        "MaxSpeechDuration": "12000"
    }
```

I can't get AWS Connect to work with multiple Lex V2 bots.

Relevant content