Hi, Thanks for highlighting the issue with custom payload. We have identified the issue and fix is being worked on highest priority. The fix will be available by 9/23.
The v2 bots I have before that date are in production and sounds like creating a new one will not help. I would open a case with AWS and have them confirm and fix the issue.
Interactive message sent in a response to a fulfilled intent breaks AWS Connect flow if proxy Lex v2 bot is created after August 17thAccepted Answerasked 3 months ago
Getting error message: The intent named 'IntentName' in bot 'BotName' is not allow listed for explicit next actions. Remove any explicit next actions from the intent and try your request again.asked 4 months ago
Amazon Lex V2: How to identify slack user-id in lambda connected to Amazon Lex v2 botasked 6 months ago
scheduling a AWS lex intent as push notification.asked a year ago
How best to add a Lex v2 bot to a swift project?asked 17 days ago
Is there a way to grab a user's voice utterance from an Amazon Lex V2 bot using Lambda calls?asked 8 months ago
Amazon Connect & Lex V2 Voiceasked 7 months ago
Amazon Lex and Cloudformation Compatibility Problemsasked 3 months ago
Amazon lex Chat Bot testAccepted Answerasked 2 months ago
Lex Response Cards in Amazon Connect ChatAccepted Answerasked 2 years ago