Hi all! I tried to reproduce this bug but I am completely incapable of doing so. What kind of “chrome” are we talking about here? Desktop Chrome? Mobile Chrome? Chromebook Chrome?
Also the OS might be interesting to know since it might do something funky with the OS browser caches.
You could also test if the browser caches are the culprit by appending some trash to the query string. E.g.: https://,ypage.com/autologin_link=xxxx&trash=1234
The “trash=1234” bit should prevent the browser from being able to identify that a given page has been visted already and force a reload.
Like I said: I have no clue why this is happening to you. Thanks for reporting, but I need something to work with to fix the issue.