Issues with glide.ui.session_timeout

[nluoma]

We recently upgraded to Utah and are running into odd issues.

Users are reporting that sometimes when they update a record, instead of saving the record, it will refresh, and they'll be in a new (blank) record.

I've narrowed it down to users who are opening a record, then after a period of time (no one can give me a specific amount, but I'm guessing as much as 15 minutes to half an hour.)

I assumed it was the glide.ui.session_timeout setting and wanted to check what it was set to.

However, I can't find that permission in my sys_properties (on any of my instances.) Since we started on Berlin, it might not have gotten added (if it was added later). But is there any other reason people can think of why it would be gone?

I was planning to check a new developer instance to see what it should look like and recreate it. Is there any reason I shouldn't do this?

Thanks!

[Ratnakar7]

Hi @nluoma ,

There are a few reasons why the glide.ui.session_timeout setting might not be visible in sys_properties.

One possibility is that the setting was never added to your instance. This could be because your instance was upgraded from an earlier version of ServiceNow that did not have the setting.

Another possibility is that the setting was removed from your instance. This could be because the setting was causing problems, or because it was no longer needed.

Finally, it is also possible that the setting is hidden. This could be because the setting is sensitive, or because it is not intended for use by end users.

If you are unable to find the glide.ui.session_timeout setting in sys_properties, you can check a new developer instance to see what it should look like. If the setting is visible in the new developer instance, you can try recreating it on your production instance.

Session activity timeout (instance security hardening) 

Thanks,

Ratnakar

[Bert_c1]

Hi,

that system property value is 90 minutes in my PDI.  There is also the Transaction Quota Rule named "UI Transactions" that is 298 seconds.  It likely this quota rule.

https://[instance_name]/sysrule_quota_list.do?sysparm_query=name%3DUI%20Transactions&sysparm_view= 

https://docs.servicenow.com/search?q=Transaction%20quotas

You may want to check the 'System Logs' -> 'Transactions (All Users)' module. You can filter on User. Or a related log.  With enough specific details, create a Support Case for this.  They can find what occurred via node logs. Admins can also download Application Node logs and review those themselves.