1) Use Case
We are leveraging a headless SDK for our chat application. Consider the following scenario:
- In Browser Window A, we initiate the
MessagingService.startConversation command and listen to the MessagingService.messagesReceived event to receive messages.
- In Browser Window B, we want to continue the same conversation. However, when we call the
MessagingService.startConversation command in this window, we receive an error stating: "There is an active conversation."
2) Query: How to Check for Active Conversation
We need to understand how to determine whether a conversation is already active so we can handle such cases appropriately.
3) Conversation Initialization Behavior
As per our flow:
- We first invoke the
configureConversation command.
- Then we call the
joinConversation command (which works only if it's a new session).
In our case, when we call configureConversation, it returns newSession: false.
Question: How should we proceed to start or join the conversation when newSession is false?
4) Issue After Ending Conversation
During a live conversation, we use the clearConversation command to end the conversation.
However, after that, when we call configureConversation, it still returns an error: "There is an active conversation."
#API/Integrations#ArchitectureandDesign#DigitalChannels#Implementation------------------------------
Haridass Sarangan
------------------------------