@Nathan CCC Thank you for your help. The thing is that, right now, the error is no further happening. However, it affected all users no matter if they enter through Reports and Analytics or {url}/analytics. The workaround we applied was entering through {url}/xmlpserver/servlet/home. Browsing using incognito/private mode…