In doing some troubleshooting to work out why auth users are being shown a "continue" prompt rather than new conversation, my suspicion is that sending the database.set command before the end user actually opens the launcher is actually starting that conversation.
Is this correct and how have you all handled it?
Hello,
The developer mainly focuses on questions related to APIs, SDKs etc. The Genesys Cloud Community Forum is a more appropriate place for general configuration questions.
Best
Hi Ebenezer I'm not sure why you're referring me to the Community Forum here as my question is directly related to an SDK command.
My bad, I wasn't sure which service you are inquiring about. Can you be more specific so I can ask the right team for help?
Thanks
Web Messaging as per the forum name 
Any ideas anybody?
Okay so the issue here isn't the database.set but is in the web developers initiating an auth request through the SDK separately to the end-user interacting with messaging. That request creates a new conversation.
Hello,
Could you share with us how you got ride of this situation ?
Thx by advance
@VaunMcCarthy we are checking this: can you confirm whether you have enabled Auto-Start in your Messenger configuration?
Yep, auto start is in place so that the bot flow starts immediately. To confirm, I see a conversation started before they've even clicked the launcher button so I can only assume the process of exchanging tokens and obviously the authentication itself enabling the launcher button is creating a conversation.
Right - thanks for raising this, we are revisiting internally.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.