Understanding the Relationship Between Integration Session PropertiesIssue Critical Timing Relationship It is crucial to understand that the timer for glide.integration.session_timeout must be exceeded before glide.integrations.active.session.life_span comes into effect. This relationship is fundamental to the proper functioning of integration session management in ServiceNow. Key Points glide.integration.session_timeout acts as a prerequisite for glide.integrations.active.session.life_span.The active session lifespan only becomes relevant after the inactivity timeout has been surpassed.This mechanism ensures that active sessions are not prematurely terminated due to brief periods of inactivity. SymptomsPractical Examples To illustrate this concept, let's consider two scenarios: Scenario 1: Active Session Lifespan Does Not Take Effect Configuration: glide.integration.session_timeout = 30 minutesglide.integrations.active.session.life_span = 120 minutes Example: An integration starts a session at 9:00 AM. The session remains active with consistent activity until 10:45 AM. Here's the sequence of events: The session has been active for 105 minutes (from 9:00 AM to 10:45 AM).At 10:45 AM, the last activity occurs.The system starts counting the 30-minute inactivity period (glide.integration.session_timeout).If no activity occurs, the session would terminate at 11:15 AM due to inactivity.However, let's assume new activity occurs at 11:10 AM, resetting the inactivity timer.The session continues to be active, and the process repeats. Key Points: glide.integrations.active.session.life_span does not come into effect because the timer on glide.integration.session_timeout never expires.As long as there is activity within each 30-minute window, the session remains active indefinitely.The active session lifespan is not triggered, as it requires the inactivity timeout to be exceeded first. In this case, glide.integrations.active.session.life_span never influences the session's lifecycle because consistent activity prevents the inactivity timeout from being reached. Scenario 2: Session Timeout Occurs Before Lifespan Limit Configuration: glide.integration.session_timeout = 15 minutesglide.integrations.active.session.life_span = 60 minutes Example: An integration initiates a session at 2:00 PM. The session is active until 2:10 PM, then becomes inactive. Here's what happens: At 2:25 PM (25 minutes after session start), the session is terminated.The termination occurs because glide.integration.session_timeout (15 minutes) was exceeded.glide.integrations.active.session.life_span never comes into effect because the session didn't remain active long enough. In this scenario, glide.integrations.active.session.life_span didn't influence the session's lifecycle because the inactivity timeout occurred first. ReleaseAll Versions.ResolutionImportance of Proper Configuration Understanding this relationship is crucial for system administrators to: Prevent unexpected session terminations.Optimize system resources by balancing session longevity and timely termination.Ensure security by limiting the duration of potentially vulnerable active sessions. By carefully configuring these properties, administrators can create a robust and efficient integration session management strategy that aligns with their organization's needs and security policies. It's important to note that glide.integrations.active.session.life_span serves as a safeguard against indefinitely active sessions, but it only comes into play when the inactivity timeout is reached.