Commander sessions time out unexpectedly

Commander and Service Portal sessions automatically log out after a period of inactivity to maintain security. These timeouts are configurable, but users may notice unexpected early logouts. This article explains how to configure session timeouts and provides troubleshooting steps if timeouts occur sooner than expected.

Configuring session timeouts

From the Configuration menu, choose System Configuration.
Switch to the Authentication tab.
Click Edit under Session Preferences.
Enter a value in seconds, minutes, or hours for Commander and/or the Service Portal and click OK.

Troubleshooting session timeouts

If session timeouts occur earlier than expected after confirming the settings above, follow these steps:

Close all browser windows.
Multiple browser windows can create session conflicts, causing premature logouts. Close all windows, then open a new browser window and check if the issue persists.
Clear your browser cache.
Cached data can trigger session timeout issues. Use your browser’s help files for clearing the cache or use a tool such as Piriform's CCleaner to clear cached data across all browsers.
Check your system time.
System time discrepancies compared to Commander’s application server or your Domain Controller can cause session errors. If the difference exceeds 2 minutes, coordinate with your network administrator to synchronize the time.

If problems persist, generate and send Commander diagnostics to Snow Software Technical Support, including a description of the issue.

Outcome

Following these steps ensures session timeout settings are properly configured and minimizes the risk of premature logouts.

Was this helpful?

Product

Snow Commander

Solution Area

Initial Configuration

Visibility

Guest

URL Name

whyaremycommandersessionstimingout