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
Chat Interface does not take the same user input more than once - partly due to the structure of the runtime engine.
Currently every time a variable changes within the runtime engine, the state of the Chat interface component changes so that it can keep track of chat interaction data. However, this results in the component displaying the same messages every time the state changes. To counteract this, currently, we filter out the interaction data that has the same id and the same message value. This works fine until you try to send the same message again - the message will not be shown on the chat interface since it is filtered out as redundant. This is because the id of the message is tied to the input component that provides the chat interface with the message string which does not change unless the input component is different - so if the the same string is more than once from the same input component it'll have the same id and value and the subsequent message string is not shown
The text was updated successfully, but these errors were encountered:
Chat Interface does not take the same user input more than once - partly due to the structure of the runtime engine.
Currently every time a variable changes within the runtime engine, the state of the Chat interface component changes so that it can keep track of chat interaction data. However, this results in the component displaying the same messages every time the state changes. To counteract this, currently, we filter out the interaction data that has the same id and the same message value. This works fine until you try to send the same message again - the message will not be shown on the chat interface since it is filtered out as redundant. This is because the id of the message is tied to the input component that provides the chat interface with the message string which does not change unless the input component is different - so if the the same string is more than once from the same input component it'll have the same id and value and the subsequent message string is not shown
The text was updated successfully, but these errors were encountered: