Timeout settings

[markdart]

Hi I am working with a company that insists on havinga  timeout set at 15 minutes. We are having an issue with sessions timeing out in the middle of typing. I had one today in the middle of working on a flow in dev.

We are on Yokohama and I have logged this issue with Servicenow. They made this suggestion

We recommend that active session timeouts ('glide.ui.active.session.life_span' and 'glide.guest.active.session.life_span') be set to 2x to 3x the respective inactive session timeouts ('glide.ui.session_timeout' and 'glide.guest.session_timeout'

I set below and the the issue seemed worse.

Glide.ui.session_timeout set to 15 Minutes
Glide.ui.active.session.life_span to 30 Minutes

Any other suggestions 

[Ankur Bawiskar]

@markdart 

My thoughts

-> Increase glide.ui.active.session.life_span: Set the value significantly higher than the inactive timeout. If the business demands a 15-minute inactivity timeout, consider 60–90 minutes for active session lifespan.​

-> Educate Users: Remind users that long periods of typing without saving changes might cause perceived “activity” but not reset the inactivity timer—saving, navigating, or interacting (AJAX/network request) resets it

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[Deepak Shaerma]

Hi @markdart 

• glide.ui.session_timeout (Inactive Timeout): This is your "idle" timer. It means: "If the user does nothing (no clicks, no server calls) for this many minutes, log them out."

  • You set this to 15 minutes per your company's rule.

• glide.ui.active.session.life_span (Active/Hard Timeout): This is the maximum, total, non-negotiable lifetime of a session. It starts counting the moment you log in. It does not care about activity.

  • You set this to 30 minutes.

This is the problem: You have created a 30-minute "hard" limit on all sessions. A developer who logs in at 9:00 AM will be guaranteed to be kicked out at 9:30 AM, even if they are in the middle of typing a script.

Before your change, this "active" property was probably set to the default (1440 minutes, or 24 hours), so you only had to worry about the 15-minute idle timeout. You've now added a second, much more aggressive timeout that punishes active work.

So Solution that i recommended is to go back to your sys_properties table and change glide.ui.active.session.life_span back to a large number. The default is 1440 (24 hours). If you must set it, set it to at least 480 (8 hours), but 1440 is standard. This will stop kicking people out after 30 minutes of active work.
2. Navigate to sys_properties.list in your filter navigator -> Click New (or search for the property if it already exists).

• Name: glide.session.trigger.interval

• Type: integer

• Value: (This is in seconds). The value must be less than your inactive timeout.

  • Your inactive timeout is 15 minutes (which is 900 seconds).

  • A good value is 1/3 or 1/2 of your timeout. I strongly recommend 300 (which is 5 minutes).
    
    

Note: Please Mark this Helpful and Accepted Solution. If this Helps you to understand. This will help both the community and me..
- Keep Learning ‌‌
Thanks & Regards 
Deepak Sharma

[markdart]

THanks for the very indepth response, I have implemented your suggestions and will monitor

[Deepak Shaerma]

Thanks for the feedback,

Please Mark this Helpful and Accepted Solution. If this Helps you to understand. This will help both the community and me..
- Keep Learning ‌‌
Thanks & Regards 
Deepak Sharma