Stale data after a long session is almost always a browser cache issue, not a nouz server issue. Three layers of refresh, ordered by how aggressively they clear cache.
01 When this happens
After a long tab session — hours of leaving nouz open in a browser tab while doing other things — the cached page can drift behind the database. You see yesterday's tile when today's data exists, or an entry you just deleted on your phone is still showing on desktop.
02 Hard refresh
The fix depends on which level the cache is at:
- Normal refresh (F5 / Cmd+R) — clears most in-memory state. Try this first.
- Hard refresh (Ctrl+Shift+R / Cmd+Shift+R) — also clears the browser disk cache. Use if normal refresh doesn't help.
- Close and reopen the tab — equivalent to hard refresh but more thorough.
03 When hard refresh doesn't work
If hard refresh + tab reopen still shows old data, log out and log back in. That clears every cookie + cached state and starts the session from scratch. Should resolve any lingering cache issue.
04 Multi-device sync delay
When you log an entry on your phone and then check your desktop, the desktop may show the older state until you refresh. That's not a bug — the desktop's currently rendered page is from when you loaded it, and doesn't auto-poll for changes. A normal refresh on the desktop picks up the phone-logged entry immediately.
Was this article helpful?
Your vote helps us decide what to write next.