In your case, the best path forward is to delete the impacted intent and recreate a new intent with same settings. Also, we have deployed a fix to console and this problem should not occur again.
Sorry about the churn and we hope this unblocks your development.
Error on creating intent after createbotlocaleasked 10 months ago
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 3 months ago
CreateBotLocale is erroring with user has no permissionsasked a year ago
Error when testing Lexbot with Kendra Search IntentAccepted Answerasked 2 months ago
scheduling a AWS lex intent as push notification.asked a year ago
AWS Lex is not recognizing user intentasked 7 months ago
Error when using Amazon Lex chatbot with Amazon Kendra on the AWS Cloud Quick Start Reference Deploymentasked 10 months ago
Add intent to botasked 3 years ago
Getting error on Lex Bot CreationAccepted Answerasked 3 months ago