Error Reference

Session timeout: your session has expired

Session timeout: your session has expired

Where this appears

This error appears in the ServiceNow user interface when attempting to perform actions after a session has expired, typically displaying as a modal dialog or redirect to the login page. It can also appear in system logs when automated processes or service accounts encounter token expiration issues during API calls or scheduled jobs.

Sourdough
Chrome Extension

Debugging this in a real instance?

Sourdough lets you trace "Session timeout: your session has expired" through system logs, script errors, and API health in the ServiceNow tab you are already using.

Add to Chrome

Free to install. Pro $5/month after a 14-day no-card trial.
Pro requires the ServiceNow admin role. Upgrade inside the extension.

Overview
Tasks
CMDB
API
Metrics
Monitor
Internals
Instance:sourdoughdev·Version:Yokohama
Instance StateONLINE
System StatusFully Operational
Session Timeout90 minutes
Logged-In Sessions2 (20 active)
Build Nameyokohama-12-18-2024_p1
IP Address10.159.128.43
Instance HealthHealth Score: 90%
🔥 5dSourdough (Chrome Plugin)Dark Mode

Cause

User session exceeded the configured idle timeout limit due to inactivity, which is controlled by the 'glide.ui.session_timeout' system property. (high likelihood)

User session exceeded the absolute session timeout limit regardless of activity, controlled by the 'glide.authenticate.sso.max_session_timeout' system property. (high likelihood)

Service account or integration user token expired during API calls or scheduled operations, particularly when OAuth token expiry is set too low. (medium likelihood)

Browser-stored session cookies were cleared, corrupted, or expired independently of ServiceNow session management settings. (medium likelihood)

System maintenance, instance restart, or node switching in a clustered environment invalidated active sessions unexpectedly. (low likelihood)

Fix

Step 1: Navigate to System Properties > Session Management and check the current values for 'glide.ui.session_timeout' (idle timeout) and 'glide.authenticate.sso.max_session_timeout' (absolute timeout).

Step 2: Review the System Log at System Diagnostics > Log > Application Log to identify if the timeout occurred during specific operations or affects multiple users.

Step 3: If affecting service accounts, check OAuth Application Registry at System OAuth > Application Registry to verify token expiration settings and refresh token configuration.

Step 4: For frequent user timeouts, consider increasing the idle timeout value in 'glide.ui.session_timeout' from the default 30 minutes to a more appropriate duration for your organization.

Step 5: Verify if SSO integration is causing premature session termination by checking Identity Provider session limits and SAML assertion validity periods.

Step 6: Clear browser cache and cookies for the ServiceNow instance, then test login again to rule out client-side session storage issues.

Step 7: Monitor active sessions using System Diagnostics > Sessions Active to identify patterns in session termination and validate that timeout adjustments are working correctly.

Test Your Knowledge

Quick 3-question quiz. See how your ServiceNow skills stack up.

Question 1 of 3Performance

A list view on a table with millions of records is slow. Best fix?

Select an answer to continue