"Session Expired (401)" after upgrading to Washington. Is anyone else getting complaints on this?

[bostonsnow]

Since upgrading to Washington DC my users have started seeing a "Session Expired (401) popup on their browser when their session expires. I'm assuming this was enabled or released with this version because it never appeared prior to the upgrade. If you have multiple browser tabs open this popup will appear on each browser tab. I'm getting a lot of complaints from my user base on this. Our timeout hasn't changed but they are seeing the popup now so they are asking that the timeout gets extended so they don't see the popup. Personally I think the popup is a good thing because it prevents users from making updates and losing them when they click Save or Update on an inactive session. I've been burned by this many times making KB updates. 

My question is, is anyone else getting complaints from their user base on this popup? If so, did you do anything to address it?

[Sandeep Rajput · Accepted solution]

@bostonsnow This popup for session timeout appears on the UI for the instances where the property "glide.ui.polaris.experience" is enabled. For instances above San Diego, this property seems to be enabled by default.

Source: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1437660

To adjust the session timeout at instance level you need to adjust the property glide.ui.session_timeout. Please refer to https://docs.servicenow.com/bundle/xanadu-platform-security/page/administer/security/reference/sessi... for more details.

In my personal opinion this pop up is a good indicator to inform the users about session timeout. I recommend you to educate the users about this pop up via KB articles.

Please mark the response helpful and accepted solution if it addresses your question. 

[Sandeep Rajput]

@bostonsnow Please accept the response as solution if you have no further questions.

[bostonsnow]

Thanks Sandeep. I agree. Would the upgrade to Washington have reenabled this or maybe is was disabled by default in San Diego then enabled by default in Washington? This was never enabled across our instances.

[Sandeep Rajput]

@bostonsnow This popup is by default available in the Next Experience UI. It was never part of the UI 16. Have you recently enabled the Next Experience (Polaris UI) for your users?