In the Virtual Agent stuck on loading when a user also opens a portal VA windowIssue A customer reported an issue of when a user tests VA topics in the VAD, and then reloads the portal window, the VA does not load. It remains blank.ReleaseAnyCauseThis is expected behavior. When a user opens a conversation in the portal, it will result in the VA web client in the portal attempting to access any existing current conversation for that user. Since there is an active conversation in VAD in preview mode, the handshake between the web client in the portal will throw the following warning and exception. This occurs to prevent preview mode conversations from being continued in the portal. 2024-08-21 13:39:38 (794) Default-thread-15 3640331BC3841E90073125AEB00131E7 txid=e7b2f397c308 SilentHandshake WARNING app="CI" track="VA" Attempting to access a preview topic outside of preview mode That warning also leads to this exception: [code]<pre style='width:fit-content,overflow:scroll'> com.glide.rest.processors.UnAuthorizedException: Unauthorized access to topicat com.glide.cs.qlue.module.coma.SilentHandshake.process(SilentHandshake.java:224)at com.glide.cs.qlue.module.coma.SilentHandshakeNowAssist.process(SilentHandshakeNowAssist.java:94)at com.glide.cs.qlue.module.coma.SessionServiceImpl.executeSilentHandshakeNowAssist(SessionServiceImpl.java:252)at com.glide.cs.qlue.module.coma.SessionServiceImpl.createSessionV2(SessionServiceImpl.java:62)at com.glide.cs.qlue.module.coma.SessionResourceV2.createSession(SessionResourceV2.java:59)at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)at java.base/java.lang.reflect.Method.invoke(Method.java:568)at com.glide.rest.handler.impl.ServiceHandlerImpl.invokeService(ServiceHandlerImpl.java:44)at com.glide.rest.processors.RESTAPIProcessor.process(RESTAPIProcessor.java:345)at com.glide.processors.AProcessor.runProcessor(AProcessor.java:762)at com.glide.processors.AProcessor.processTransaction(AProcessor.java:313)at com.glide.processors.ProcessorRegistry.process0(ProcessorRegistry.java:187)at com.glide.processors.ProcessorRegistry.process(ProcessorRegistry.java:175)at com.glide.ui.GlideServletTransaction.process(GlideServletTransaction.java:58)at com.glide.sys.Transaction.run(Transaction.java:2734)at com.glide.ui.HTTPTransaction.run(HTTPTransaction.java:35)at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)at java.base/java.lang.Thread.run(Thread.java:8</pre>[/code]ResolutionIn order to avoid this, you need to finish any in-progress conversations in VAD before trying to engage in conversations in the portal. This is expected behavior. A workaround we did find that will get the VA to load again and end the conversation. 1. Open Virtual Agent Designer and select the LLM assistant3. Click "Test active topics" and then just close the popup without any action