@Krishna Madireddy

even if the access group timeout is blank, Pega still has a platform-level requestor timeout that can end sessions by default (typically via DSS keys like prconfig/timeout/browser/default and prconfig/timeout/application), so check and standardize those values first.  In Constellation, confirm the access group inactivity setting is truly unset for the operator’s active access group (and any others they can switch to), because that setting will warn, then log out on idle.  If you use SSO/OIDC, verify the Authentication Service: enable “use access group timeout” if you want Pega to control idle behavior, and make sure token lifetimes/refresh are not expiring earlier than you expect.  Check that no portal or harness includes pxSessionTimer, which can independently trigger logout even in Constellation if it’s embedded somewhere from older rules. Recommended cleanup: pick a single policy, set the desired idle timeout in the access group, align or remove conflicting DSS prconfig timeouts, avoid custom session timer sections, and retest. If the session still drops, capture logs/network calls to see whether an IdP token expiry or refresh failure is forcing re-authentication despite Pega settings.