AWS Lex V2 not invoking slot type values after user input yes

0

AWS Lex not invoking slot type values after user input "yes". I have already selected the desired slot type within Intent->slots. still it is not recognizing during chat: "intent": { "name": "ICLIGM", "slots": { "Modules": null }

I am repeatedly getting slot prompt message inspite of user input "yes".

{ "content": "Do you want to see ICLIGM Module details?", "contentType": "PlainText" } ], "sessionState": { "dialogAction": { "type": "ElicitSlot", "slotToElicit": "Modules" }, "intent": { "name": "ICLIGM", "slots": { "Modules": null }, "state": "InProgress", "confirmationState": "None" }

  • Can you give some details about the slot (type, values, etc)

  • I observed "resolvedValues" are not displayed on chat. We can see clearly on Inspect / Log: { "messages": [ { "content": "Here are the details: import module ", "contentType": "PlainText" } ], "sessionState": { "dialogAction": { "type": "ConfirmIntent" }, "intent": { "name": "ICLIGM", "slots": { "ImpConf": null, "ImpModule": { "value": { "originalValue": "import module", "interpretedValue": "import module", "resolvedValues": [ "ICLIGM Import Module takes care of complete Import procedure and documentation required for Customs and Ports " ]

profile picture
asked 2 months ago114 views
1 Answer
0

Your bot is in a dialog state of ElicitSlot for Modules. There does not seem to be any slot values set at that point. What values do you have for Modules- it is just Yes/No, or do you have others? If the bot cannot recognise what the user says as being a match for the slot it will keep repeating the prompt.

AWS
Gillian
answered 2 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions