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 does the app show old data?
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 How do I do a hard refresh?
Which refresh you need depends on how deep the stale cache is. Start with a normal refresh (F5 / Cmd+R), which clears most in-memory state. If that doesn't help, do a hard refresh (Ctrl+Shift+R / Cmd+Shift+R), which also clears the browser disk cache. Closing and reopening the tab is equivalent but more thorough. Work down the list below until the data updates.
- 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 What if a hard refresh doesn't work?
If a hard refresh and a tab reopen both still show old data, log out and log back in. That clears every cookie and cached state and starts the session from scratch, which resolves any lingering cache issue the lighter refreshes couldn't. Stick to logging out of nouz specifically — don't clear all your browser cookies, since that logs you out everywhere, not just here.
04 Why does my desktop lag behind my phone?
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.