You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During the development of our QnABot, we observed that the Lex Web UI requires a variable amount of time to initialize, ranging from a minimum of approximately 4 seconds to a maximum of 10 seconds, before it begins posting the initial message. This latency results in a noticeable delay before users are presented with functional content on the screen, which has led to concerns regarding the user experience.
Upon thorough examination of the QnA Bot's codebase, we have identified that the mounting process is preceded by a Promise.all call, as detailed below.
To get Bot metadata from "api-stage".
To Authenticate using "cognito-idp".
Are there opportunities for streamlining these steps, or could we implement any configuration modifications to enhance the speed of the same?
The text was updated successfully, but these errors were encountered:
Hi @DiljithNair
Is this issue related to the embedded Lex_Web_UI in QnaBot (accessible from the content designer)? .
We did not see that delay.
Can you confirm the version of QnABot you are using and the steps to reproduce if different than the attached screenshot?
Also the embedded Lex_Web_UI is mainly for testing. Our recommendation is to use the https://github.com/aws-samples/aws-lex-web-ui for your customers either as standalone or embedded into your web page.
During the development of our QnABot, we observed that the Lex Web UI requires a variable amount of time to initialize, ranging from a minimum of approximately 4 seconds to a maximum of 10 seconds, before it begins posting the initial message. This latency results in a noticeable delay before users are presented with functional content on the screen, which has led to concerns regarding the user experience.
Upon thorough examination of the QnA Bot's codebase, we have identified that the mounting process is preceded by a
Promise.all
call, as detailed below.Are there opportunities for streamlining these steps, or could we implement any configuration modifications to enhance the speed of the same?
The text was updated successfully, but these errors were encountered: