@SvenKrow

Here’s the thing: in Constellation the server session only stays alive when the browser makes a server call (DX API, data page load, save, validate). Pure client clicks on radio buttons or typing in text boxes don’t hit the server, so the platform sees 15 minutes of inactivity and logs the user out. To fix it, first align and, if allowed, increase timeouts at the shortest hop: Pega requestor timeout (DSS/prconfig timeout/requestor) and Access Group Authentication timeout, plus your IdP/OIDC token lifetimes if you use SSO—the smallest wins. Next, make the screen generate lightweight server traffic: enable autosave on the editable view, add “Post value”/“Save” or “Run data transform” on key field changes, or reference a data page in the view that reloads every 5 minutes (“Reload if older than” → used by a hidden read-only field) so a DX call lands periodically. Avoid custom JavaScript heartbeats; Constellation doesn’t support them. Turn on the timeout warning so users get a prompt before expiry and can extend the session. Verify in the browser Network tab that you see periodic DX API requests while the user is active. Finally, clear any security review—auto-keepalive may conflict with your org’s idle-logout policy.