Chrome is tricky... instead of using 'flat files' for website cache's (storing often viewed pages so they load faster) Chrome uses a database entry, and that database isn't stored on your local machine- it's stored in google's cloud... the 'entries' for that database's tables ARE stored on your local computer... all in the name of speed (loading speed)...
i've went around my elbow to arrive at my bedonkeedonk several times now trying to put some speed to this joint...
but i am willing to wager your issue is with chrome's cache and the browser files....
what to do (and it may be a good idea to do this anyway, as several pages you visit may have changed since the last capture) :
first, hold your ctrl button click refresh... that should clear some things for you (and if you haven't done this in a while, stand by because the site has changed some in the last month)... this ^ should do it, but may not... in this case:
click your three dots top right corner of browser- select (hover) "more tools", then 'clear browsing data', and select the parts and pieces you want to clear.... you're going to want to focus on "browsing history".
if that doesn't do it, let me know.... like i said, chrome/google is tricky and sometimes you gotta play 'not nice' with them to clear data they are tracking you with.
I injected some code some time back to remedy the 'sessions time out' thing, and i fear it's still alive in cache's on user's computers (or googles cloud)- which would/will cause the issue you're seeing.
