Alert in the browser: "Your session has expired. Click OK to log in again."
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-09-2016 06:20 AM
When a user whose session has timed out tries to open any page, they sometimes get the following message in the form of an alert: "Your session has expired. Click OK to log in again." This does not happen every time. Sometimes authentication happens automatically, i.e. without this popup. I am trying to figure out what triggers that message and under what circumstances. However, all I could find so far was the UI Message "ajax_session_timeout_goto_login_confirm". Can anyone give me a hint please?
Blog: https://sys.properties | Telegram: https://t.me/sys_properties | LinkedIn: https://www.linkedin.com/in/slava-savitsky/

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-09-2016 06:24 AM
Hi Slava,
I did some searching on the wiki for this error message and found these. Hopefully there is something of use here.
Session expired message on login for end users
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-09-2020 12:20 PM
Funny, we have the opposite issue. We are now in Madrid (off-prem-cloud), and if the session goes stale, the system doesn't let you know.
This results in continued work on a ticket, Knowledge article, or whatever work, only to find when you press "Submit" that the screen refreshes and all is lost with no heads up that you were attempting to work in a timed-out session. Save early, save often!!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-21-2020 09:10 AM
Hello Michael. We are also having the same issue in our Madrid instances. Did you find a solution?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-24-2020 03:54 PM
No Katie. I'm not even sure if anyone's cared to report it as it seems like the typical "Working as designed" behavior we see in our system.