- Newest
- Most votes
- Most comments
Hi,
The error message "The specified resource 'PizzaOrderTestBot' does not exist" indicates that the bot named "PizzaOrderTestBot" could not be found in your AWS account. Make sure that you have created the bot and that you have specified the correct name when you configured the web UI.
Regarding the "The slot to elicit is invalid" error, this message indicates that your bot is trying to elicit a slot that is not defined in your bot. This could happen if the slot name has been misspelled or if the slot has been deleted from your bot.
To troubleshoot this issue, check the logs in CloudWatch Logs for your Lex bot to see if there are any errors or exceptions being thrown. You can also try testing your bot in the Lex console to see if you encounter the same error.
If the problem persists, you may need to update your bot's configuration to ensure that all the required slots are defined correctly. Make sure that the slot names and types are correct and that the slot is marked as required if necessary. You may also need to update your Lambda function code to handle the slot elicitations correctly.
Hope it helps.
Relevant content
- asked a year ago
- asked a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 months ago
thanks for responding, dealing with "The slot to elicit is invalid" error; I tried the bot in the lex console and it works fine, but when try it in the web ui , I allways recieve the same error, and I didn't figure out the cause
Hi, could you check the logs in CloudWatch Logs for your Lex bot to see if there are any errors or exceptions being thrown when using web ui?
I already check and every thing it's ok, I retry to delete the stack and create a new stack that deal with the project and now it's running ok, I figure out that when updating the bot in aws console that does not mean there will be an automatic update in the web ui, every time I need to delete the stack an create a new one.