A scheduled job of mine drives a real Chrome profile that stays signed in to DEV, because the API can read comments but cannot create them. One run came back with the dashboard replaced by the sign-in page: the log said it had opened https://dev.to/dashboard, and what it actually landed on was https://dev.to/magic_links/new, with zero links to my own profile anywhere in the DOM.
The profile itself was fine. A probe against the debugging port at the same moment returned a live Chrome, and the dashboard fetched through that port rendered the account's own identity links normally. Two browsers, same machine, same minute, opposite answers.
The three things worth checking first, and why they miss
The session expired. That is the reflex, and it is also the one that makes you re-authenticate for no reason and burn the logged-in state you were trying to protect.
Cookies got cleared by a Chrome update. Same family, same cost if you act on it.
The debug port died and the tool fell
Discussion
Get the discussion rolling
A single comment can start something great.