Resolving Extended Session Duration and Performance Issues with Shared Service AccountsIssue Multiple applications and integrations are using a single service account (e.g., SNOWSVCACCT), leading to:- Extended session durations- Session ID reuse across applications- Overloaded nodes- Disrupted load balancing for API requestsSymptomsSession ids are not terminated within the expected time frame. syslog_transaction shows a single session id being used by more than one application.Incoming transaction are not being properly distributed across all nodes in the cluster due to session id reuse.ReleaseAll.CauseMultiple applications and integrations are using a single service account (e.g., SNOWSVCACCT), leading to:- Extended session durations- Session ID reuse across applications- Overloaded nodes- Disrupted load balancing for API requestsResolution1. Create separate service accounts for each application or integration: - Navigate to User Administration > Users - Create a new user for each application - Assign appropriate roles and permissions 2. Configure each service account for API-only access: - Open the user record - Check the "Web service access only" box 3. Update application configurations: - Modify each application or integration to use its dedicated service account 4. Implement session management: - Set appropriate timeout values for `glide.ui.session_timeout` and `glide.integration.session_timeout` - Consider using the "Limit Concurrent Sessions" plugin for additional control 5. Monitor and audit: - Regularly review the System Logs > Transactions (syslog_transaction_list.do) for API usage patterns - Use the "Usage by Web API" dashboard to track API call distribution