Topic by Jared
This is a log showing that an AddIn was in the middle of processing an interaction when RightNow sent a logout event. The console remained logged in, but our AddIn logged itself out accordingly. What could cause this within RightNow? We've never seen this before, but it should not happen.
(4) 2013-07-18-08:17:47.368: session->ProcessIncomingMessage: <ClientResponse name="interaction.request.complete.ack" target="OM106383100000147"><EventData><Data key="interaction.id">OM106383100000147</Data><Data key="channelgroup.id">4f5a74a5459147408902848cbd2793af</Data><Data key="session.id">genesys_om-REDACTED</Data><Data key="channel.id">e3901fa02117475491e9dfd277dd69a2</Data><Data key="request.id">13741606666360352</Data></EventData></ClientResponse> (->ProcessIncomingMessages)(MessageProcessor)
(3) 2013-07-18-08:17:47.368: ProcessClientResponse: (interaction.request.complete.ack) (->ProcessIncomingMessage)(MessageProcessor)
(1) 2013-07-18-08:17:47.553: FocusNextInteraction (->FocusNextWait)(FocusNextInteractionAfterWait)
(3) 2013-07-18-08:17:55.800: View::_rnSoap_IncidentCloseListener (->OnIncidentClose)(UI Thread (AppDomain 2))
(3) 2013-07-18-08:17:55.983: View::_rnSoap_IncidentCloseListener (->OnIncidentClose)(UI Thread (AppDomain 2))
(3) 2013-07-18-08:17:59.591: Dispose (->Notify)(UI Thread (AppDomain 2))
(2) 2013-07-18-08:17:59.591: <ClientAPI>-[Logout] (->Dispose)(UI Thread (AppDomain 2))