Troubleshooting Series – Ep2 – Admin Center – Sessions

Key points

• Sessions persist after closing tabs or windows, requiring manual management through the Admin Center
• The Sessions window displays all active sessions including background tasks and allows cancellation of individual sessions or environment restart
• Administrators can cross-reference Database Locks with Sessions to identify which user or process is causing performance issues
• Cancelling sessions should be done carefully to avoid incomplete transactions; restart is a last resort for critical situations
• Access requires delegated admin role or appropriate Admin Center permissions

Quotes

• “sessions are not stopped when you close a tab or window” (Explains why the Sessions window is necessary for managing long-running processes that continue consuming resources after user disconnection)
• “Cancelling a session abruptly can lead to incomplete transactions or data inconsistencies. So make sure you know what you’re doing.” (Highlights the critical best practice of proceeding cautiously when stopping sessions to avoid data integrity issues)
• “Restart is a last resort. It stops all processes so reserve this for critical situations where cancelling individual sessions didn’t resolve the issue.” (Establishes the escalation hierarchy for session management, distinguishing between targeted cancellation and environment-wide restart)

AL objects mentioned

As named in the post. A name that matches one object page by exact type and name links to it; the others stay as named.

• table “Active Sessions”

Not found in BC28-30: table “Active Sessions”.

Context

• Features: Sessions window, Cancel sessions, Restart environment, Monitor active sessions, Cross-reference Database Locks

Source: waldo’s blog, community blog. Summary, key points and quotes are derived (CONTENT-NOTICE.md); read the original for the full text.