I'm pretty sure that since a month or so, SEDE seems much more eager to get rid of my session and log me out in that process.

I don't mind logging in a couple of times per day, if that helps to reduce resource consumption, but the user experience isn't all that great when it happens.

Here is why: I'm most often in the middle of writing a query for an MSE question, for example this one. So I have the edit window open and am creating a new revision of my query. When I click "run," I do notice the button gets grayed-out, as it normally does, but I never get any result back. There is also no error message.

To recover from this I have to copy the SQL text I have typed, open a new tab and load SEDE, log in, switch back to the stalled tab, refresh, paste the SQL text, run query. Repeat the process after 10 minutes.

If the intended behavior is to log users out of their session on such short notice (I recall sessions lived for 24 hours), can there then be a slightly better handling in the browser of that state, so it is clear you're logged out once you click the run button?

I prefer, however, to have the longer allowed sessions back.

I'm experiencing this behavior mostly in Chrome on Win 10.

  • True, I lost the session couple of times while writing a query, even though it was matter of minutes. Ended up writing this as anonymous user. Commented Nov 20, 2016 at 20:51
  • I just never log in anymore; haven't for years. Captchas are less annoying.
    – Shog9
    Commented Nov 21, 2016 at 1:12
  • Ah, reminds me of this request.
    – Taryn
    Commented Nov 21, 2016 at 17:21
  • @bluefeet don't you now have access to the server log to see if it is indeed an app domain recycle? But it does look similar indeed.
    – rene
    Commented Nov 21, 2016 at 18:42
  • Not a dev over here @rene.
    – Taryn
    Commented Nov 21, 2016 at 18:50
  • 5
    Just pretend you're one .. I have faith in you ...
    – rene
    Commented Nov 21, 2016 at 20:10

1 Answer 1


Can't agree more. This is extremely inconvenient and causes UI malfunction:

  • If I leave a query window open, after some time it becomes inoperative - impossible to execute and the editor glitches
  • I have to login every time I visit the site - which I don't have to at other SE sites and the majority of other sites on the Net. Everyone except security-critical sites like banks at least provide an option to "remember me" when logging in.
  • 2
    Considering that the SE doesn't seem wanting to fix this problem, I would use some browser add-on to work around this session expiration problem from the client side. Btw, the data SE is an opensource tool, available here - in theory, anybody could produce pull requests for them.
    – peterh
    Commented Apr 23, 2017 at 23:25

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .