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
{{ message }}
This repository has been archived by the owner on Aug 30, 2022. It is now read-only.
Being in a channel and having the knowledge base opened. The Knowledge base is not being refreshed if new results/conversations would be available through creating new requests for the same topic in parallel.
By solving this issue the widget should be reloaded when new conversations have been created in time.
While writing these thoughts, I'm quite unsure if we really want this as a feature. I could imagine, that the user will be confused if something changes without an interaction.
Maybe it is wish of hardcore testers ;-)
The text was updated successfully, but these errors were encountered:
Implementation wise this would be possible as we do have a websocket connection open. But I agree that this feature might be confusing (or even concerning) for users.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Being in a channel and having the knowledge base opened. The Knowledge base is not being refreshed if new results/conversations would be available through creating new requests for the same topic in parallel.
By solving this issue the widget should be reloaded when new conversations have been created in time.
While writing these thoughts, I'm quite unsure if we really want this as a feature. I could imagine, that the user will be confused if something changes without an interaction.
Maybe it is wish of hardcore testers ;-)
The text was updated successfully, but these errors were encountered: