Problem:
Currently, the directline has a cache of the conversation history only for 24 hours. The conversationId which is used to reconnect to the conversation also gets obsolete after a few days/weeks, disabling the client to reconnect to the ongoing conversation.
Feature to overcome the problem:
There should be a feature that would let the client reconnect to a conversation exactly where they left off(This is possible for now but only for 24 hours), also after 24 hours or many weeks after leaving the conversation.
Problem: Currently, the directline has a cache of the conversation history only for 24 hours. The conversationId which is used to reconnect to the conversation also gets obsolete after a few days/weeks, disabling the client to reconnect to the ongoing conversation.
Feature to overcome the problem: There should be a feature that would let the client reconnect to a conversation exactly where they left off(This is possible for now but only for 24 hours), also after 24 hours or many weeks after leaving the conversation.