It’s pretty normal, that your browser cache the page contents. Technically the browser decides how long stuff will be cached. However, even when the cache is 100% invalid/stale it does not automatically trigger a refresh or a request to your server to get fresh data. That’s how browsers work. Then only thing that comes to my mind is having some cron job to get a new version and then having on a client an interval to refresh the browser. That’s not a good practice, but it would work technically

maybe when user has old data theres possibility to refresh the page?

How do you know if the page has been updated without an additional request?

I guess then you need something like a websocket or similar, but that’s also not ideal

something on page open, if data is older than 1 day, force refresh for example

because you dont need to have page opened in the tab for it to happen

Then you can do ISR. After a specific amount of time the page automatically revalidates and then it’s a new static version of the page. But keep in mind, that you get this new static version only when you refresh the page

i have isr already, but it doesnt get a new page until f5

and i should somehow store the page generation cache in the browser

its intended, that you cant see it instantly with ISR. Its like this:

1. First request after revalidation -> stale-while-revalidate -> serve old content
2. Second request after revalidation -> server new content

Which next version are you using?