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
Currently the history shows up on the sidebar sorted by created date.
However if one goes back to earlier chat and continues the conversation, the chat history does not update it to be the most recent. It remains where it was in the list in chronological order. This can be difficult for user to keep track (usually they would want to jump to the most recent chat they were in the middle of in say the previous session)
In my opinion, the chat history list should bump up the chat that was most recently engaged to be the latest chat. I looked into the code a bit and it seems the front end is doing it correctly by using sortedSessions. However the last_updated date on the chat itself doesn't seem to be changed if one goes back (thru' the chat history) and continues a previous chat. In other words, the last_updated should be modified by the server to reflect the date the user last engaged.
Thanks,
Tim
The text was updated successfully, but these errors were encountered:
Hi,
Currently the history shows up on the sidebar sorted by created date.
However if one goes back to earlier chat and continues the conversation, the chat history does not update it to be the most recent. It remains where it was in the list in chronological order. This can be difficult for user to keep track (usually they would want to jump to the most recent chat they were in the middle of in say the previous session)
In my opinion, the chat history list should bump up the chat that was most recently engaged to be the latest chat. I looked into the code a bit and it seems the front end is doing it correctly by using sortedSessions. However the last_updated date on the chat itself doesn't seem to be changed if one goes back (thru' the chat history) and continues a previous chat. In other words, the last_updated should be modified by the server to reflect the date the user last engaged.
Thanks,
Tim
The text was updated successfully, but these errors were encountered: