Normal reload may reuse cached assets. Hard refresh asks Chrome to bypass cache for that load.
Scheduled tabs often look “stuck” even when the network is fine — a service worker shell, an aggressive CDN, or a long-lived SPA cache can keep yesterday’s UI. Auto Refresh Turbo can reload normally or with cache bypass. Neither mode clears cookies by itself.
Normal reload
A normal tabs.reload is what most people mean by Refresh. Chrome may still serve cached scripts, styles, and some document responses according to cache rules. For many dashboards this is enough: data endpoints return fresh JSON, and the page paints new numbers.
Prefer normal reload when:
- The board updates cleanly on manual Refresh
- You reload often and want lower origin load
- Hard refresh previously logged you out or reset needed client state
Hard refresh (cache bypass)
Hard refresh reloads with cache bypass. Use it when a normal reload keeps a stale shell — tiles frozen, old build banners, or UI that only heals after a manual hard refresh in DevTools.
Important limits:
- It does not clear cookies or wipe login
- It can increase traffic to the origin
- Some sites still recover slowly if their own service worker reclaims control
Choosing for scheduled tabs
- Start with normal reload at a sensible interval
- If the board stays stale after several cycles, enable hard refresh once and observe
- If hard refresh fixes it, decide whether every cycle needs bypass or only occasional recovery
- If hard refresh breaks auth or filters, turn it off and fix caching on the app side if you can
For wall setups, see dashboard refresh.
Schedule, random, and stop-after-N
Hard refresh is a per-session option. It works with fixed or random intervals, with daily windows, and with stop-after-N. Outside a schedule window the session pauses with settings saved — including the hard-refresh flag — until the window opens again.
Interaction and challenge stops
Stop-on-click/type and suspicious-page stop still apply. A hard refresh mid-edit is just as disruptive as a normal one; leave interaction stop on when the tab is also used for typing. Challenge screens deserve a longer interval, not a harder reload.
Stop-after-N experiments
When you are unsure whether bypass helps, enable hard refresh with stop-after-N set to a small number. Compare the board after those cycles, then either keep bypass for production or revert to normal reload for lower load.
Multi-tab pattern
Run hard refresh only on the stubborn board. Neighbor tabs can stay on normal reload so you do not multiply cache-bypass traffic across every monitor.
How the core loop runs
Regardless of normal vs hard, timing lives in the service worker with Chrome alarms. The popup follows that schedule; an optional on-page timer is cosmetic sync, not the authority. Deep dive: how automatic tab refresh works.
Troubleshooting stale UI
If neither mode helps, check whether the page needs a different URL, a filter reset, or a full browser restart after an extension or profile glitch. Use troubleshooting for schedule pause and “stopped for no reason” cases.
Try it
Install Auto Refresh Turbo, compare one normal cycle and one hard-refresh cycle on a safe board, then pick a default.