Closed shivangisharma991 closed 6 months ago
There are a lot of things that could be happening here. Can you use the Developer tools of your browser to see if there are error messages?
There are a lot of things that could be happening here. Can you use the Developer tools of your browser to see if there are error messages?
I see only one error regarding CSP, it says blocked source for index.html. Could that be the reason?
No that's just something I need to clean up, would not effect the bot. If you can check the network traffic when it sends a call to Lex it should be hitting a /text endpoint. Can you check what is happening on those calls - it could be an issue with the Lex bot itself.
@shivangisharma991 The network tab in the developer console will show a post request against the lex service sending in the users input. Please check the http response code and the response object. Sometimes an error will be shown in the response. Regardless it would be good to review the payload being returned in the response. Could you provide the response to the post request? Also, is there a Lambda fulfillment handler being called? If yes, can you log the response being provided by the lambda handler to the lex service. Is there a publc URL we can test against?
I am not getting response of any prompt I enter on the lex-ui, not sure what is wrong or I to troubleshoot to check the issue. Any suggestion would be helpful.