asyncCustomChatUX----After Click End Chat Button Screen Requires Refreshing otherwise chat initialiazation failed about amazon-connect-chat-ui-examples HOT 6 CLOSED

Hi, can you try initiating chat with a different username? You also need to click "end chat", rather than just closing the chat window, to update the DynamoDB entry that the chat is closed.

from amazon-connect-chat-ui-examples.

@angieyu i clicked on "end chat" everythime but dynamodb updates late and when we click icon again it shows initialization failed

from amazon-connect-chat-ui-examples.

Hi @angieyu,
I am facing a similar issue when trying to initialize the Chat widget on the customer application end. The DynamoDb table does not get updated when a new chat is initiated after ending the previous chat. This makes use of the same Participant token leading to a 403 Access Denied error.

Attaching the har capture screenshot for reference.

Please let me know on how to proceed further on this?

from amazon-connect-chat-ui-examples.

Hi, on Feb 10, 2023 the asyncCustomerChatUX template was deprecated.
Please switch to using the startChatContactAPI template, and let us know if this issue still occurs

from amazon-connect-chat-ui-examples.

Resolving, due to team no longer supporting asyncCustomerChatUX example - will not fix.

Please refer to startChatContactAPI solution with Persistent chat feature:

how do we recover an ongoing session? So, if the user leaves the window and comes back, can we get into the same chat window if the session is still active?

You need to maintain the chat contact id (initial/segment contact) per use-case and supply it when starting a new persistent chat session via StartChatContact api. Ensure that the past chat is ended, as in the given example, when the user leaves the chat session, they must end that chat, either via DisconnectParticipant or StopChat.

and for sessions that are closed, in the API there is this persistent chat attributes

Persistent chat requires customers to enable chat transcript on the instance. (please check Data Storage section here). We load transcript on-demand, what that means is that customers must call the GetTranscript api to see past chat transcript via the pagination token. (How to access past chat contact transcript for a persistent chat here)

Thanks,
Spencer

from amazon-connect-chat-ui-examples.

Resolving, due to team no longer supporting asyncCustomerChatUX example - will not fix.

Please refer to startChatContactAPI solution with Persistent chat feature:

how do we recover an ongoing session? So, if the user leaves the window and comes back, can we get into the same chat window if the session is still active?

You need to maintain the chat contact id (initial/segment contact) per use-case and supply it when starting a new persistent chat session via StartChatContact api. Ensure that the past chat is ended, as in the given example, when the user leaves the chat session, they must end that chat, either via DisconnectParticipant or StopChat.

and for sessions that are closed, in the API there is this persistent chat attributes

Persistent chat requires customers to enable chat transcript on the instance. (please check Data Storage section here). We load transcript on-demand, what that means is that customers must call the GetTranscript api to see past chat transcript via the pagination token. (How to access past chat contact transcript for a persistent chat here)

Thanks, Spencer

@spencerlepine thanks, quick question. This solution you're sharing allows us to load a previous conversation's transcript when starting a new chat. But how could we connect a participant to the same chat conversation if let's say the participant refreshes the page or browses to a different site section.

from amazon-connect-chat-ui-examples.