In Pega Infinily I have created this Webchat interface and the added the Mashup code(as it is generated on the Mashup tab of the interface) in a sample webapp running on Tomcat.

<!-- ********************** Begin Pega content ********************** -->
<script src ='https://localhost:8443/prweb?pyActivity=pzIncludeMashupScripts'></script&gt;
<div data-pega-gadgetname ='PegaGadget'
data-pega-action ='createNewWork'
data-pega-action-param-classname ='Work-Channel-Chat'
data-pega-action-param-flowname ='pyStartCase'
data-pega-isdeferloaded ='false'
data-pega-applicationname ='ChatbotApp'
data-pega-threadname ='STANDARD'
data-pega-resizetype ='stretch'
data-pega-url ='https://localhost:8443/prweb/PRChat'
data-pega-action-param-parameters ='{"channelId":"bot66c445b76b24481e899b7ba4ca5bc41d"}' ></div>

<!-- ********************** End Pega content ********************** -->

When I open the Sample app, the chat console is loaded -

However, on refresh of the browser screen, the chat console loads the Resolve action. This happens sporadically and goes away on subsequent refresh.

With browser refresh this is reproduced more frequently. Initially noticed this when closing the browser and opening the chat url in browser intermittently.

Was comparing the trace of good and bad scenario. In good scenario the pxAcquireInteraction java step 2 is calling the pzCloseExpiredInteraction while in bad scenario the svcAddWorkObject activty is being called.

This looks like a problem when the channelUser, pyBotConfig and pyInteractionCase is exist in the clipboard in pega for the interaction and chat session is not able to acquire the existing session and initiate the interaction again.

Have anybody seen this before? How to get rid of this?

***Edited by Moderator Marissa to update SR Details***