Page Refresh required in Chrome after extended non-use

Thanks for sharing the additional details.

That’s different that what Nigel described on his fridge (Family Hub), so I hope you don’t mind that I’m moving this to its own thread. In Nigel’s case, after the device goes into screensaver mode, when the device later wakes from screensaver, the device status updates from while the screensaver was on aren’t reflected, but any new actions / status updates are reflected as expected. That seems to be unique to the Samsung browser on the fridge.


In your GIF, I don’t see the spinner in the bottom-left corner of the tile reflecting the attempt to send the command.

It would be interesting to open Chrome’s developer tools and watch the console logs while you attempt the commands after waking from sleep and experiencing the issue.

It might also help to see the same Diagnostics I requested from Nigel, but it’s hard to tell based on the information provided so far.

Can you think of anything else that’s special about that period of time? Just the browser running in the background? No screensaver activation or certain actions that seem to correlate with the issue occurring or anything? Any extensions installed or special customizations to Chrome (eg. flag tweaks)?

I use Chrome as my primary browser on all my devices and I’ve never come across this, so I’m wondering if there might be something else that’s unique about our configurations or how we use our devices (Windows 11 Desktop, Mac Studio, Macbook Air, Pixel 7, etc)

And if you figure out steps to intentionally trigger the issue, that would be the most helpful. If I can reproduce it, it’s much more likely I can figure out what’s going on.