I'm an unusually frequent/avid SEDE user. It's like a gourmet buffet for a self-proclaimed "data geek" like myself. Thus, I've put off reporting this problem for a while, but it's continuing to cause frustration and lost time on a daily basis.
SEDE keeps users logged in for 24 hours. My issue is that if I happen to be using SEDE 23.9 hours later, SEDE will still de-authorize me, even though the page appears to still be logged in and functioning as normal.
I'll make changes to a query, run it, and get . I figure "okay, that still runs properly, now I'll try this...", and repeat, until I eventually realize that my changes are having no effect.
The query result window still flashes and reports an execution time, and it even still lets me add/remove custom prompts as if it's working properly.
...so, it still looks like I'm logged in, unless I open SEDE on a new browser tab; only then do I see that I'm not. My actions that follow have become routine (basically copy my existing query then CTRL+Z as far as possible, and try to figure out what changes were applied before SEDE stopped working.
Personally, I'd prefer if it didn't log me out at all (like SO/SE sites/chat) or only after I haven't been active for 24 hours, but is it at least possible to make it inform the user if they've been logged out mid-session?
EDIT: Steps to Reproduce
A "cheater" way to reproduce the behaviour without waiting 24 hours is to delete the related cookies with a query window open:
- Login to the SEDE here.
- Create a new query (perhaps
select * from users where id=1) and Run Query.
Delete the cookies named
Now, return to your query window, change the query (perhaps just change the ID# in the
WHEREclause), and click Run Query again.
The query will appears to have run, the result will flash, but did not change.
Or, if the
returnurl parameter worked like it appears it's supposed to, then I could just change my "new query" bookmark to:
...and presumably I'd be re-logged-in every time I create a new query.