In a domain separated instance, why does chat transfer functionality terminate the end user chat session?Description<!-- div.margin{ padding: 10px 40px 40px 30px; } table.tocTable{ border: 1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); padding-top: .6em; padding-bottom: .6em; padding-left: .9em; padding-right: .6em; } table.noteTable{ border:1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); width: 100%; border-spacing:2; } table.internaltable { white-space:nowrap; text-align:left; border-width: 1px; border-collapse: collapse; font-size:14px; width: 85%; } table.internaltable th { border-width: 1px; padding: 5px; border-style: solid; border-color: rgb(245, 245, 245); background-color: rgb(245, 245, 245); } table.internaltable td { border-width: 1px; padding: 5px; border-style: solid; border-color: #E0E0E0; color: #000000; } .title { color: #D1232B; font-weight:normal; font-size:28px; } h1{ color: #D1232B; font-weight:normal; font-size:21px; margin-bottom:-5px } h2{ color: #646464; font-weight:bold; font-size:18px; } h3{ color: #000000; font-weight:BOLD; font-size:16px; text-decoration:underline; } h4{ color: #646464; font-weight:BOLD; font-size:15px; text-decoration:; } h5{ color: #000000; font-weight:BOLD; font-size:13px; text-decoration:; } h6{ color: #000000; font-weight:BOLD; font-size:14px; text-decoration:; } --> In a domain separated instance, why does chat transfer functionality terminate the end user chat session? Overview When an end user (who is in some lower domain) initiates a chat, and then agent user (who is in upper domain and has visibility to lower domain of end user) transfers chat to different queue, the chat is no longer available to the end user when he refresh the page or tries to continue the chat. Problem Domain separation plug-in needs to activated Log on to any out of the box Istanbul instanceSetup domain for end user Abel.Tuter as TOP\ACMESetup domain for agent user Fred.Luddy as TOPImpersonate user Abel.Tuter Initiate chat from one of the queueIn another browser logon and impersonate agent user Fred.LuddyNavigate to https://<instance>.service-now.com/$c.do and look for the incoming chatAccept incoming chat from Abel.TuterClick on Transfer connect action and select another queue, for example Product SupportNow go back to step 5 and try to continue the chat as end user Abel.Tuter or reload the chat page https://<instance>.service-now.com/$chat_support.do?queueID=<chatQueue_sys_id>&channelID=<sys_id of live_group_profile of chat> Initiated chat doesn't load anymore for Abel.Tuter. Observations: Issue appears to be caused by the fact that when the chat is transferred, the end user no longer has access to it since the chat entry is moved to higher domainDomain issues with Connect chat are fixed in Jakarta release as part of problem PRB721313. Solution Development team has confirmed that this reported issue has been already addressed in Jakarta release as part of problem PRB721313. On Istanbul instances, reported issue could be worked-around via the attached business rule.