Timed reloads can keep some web UIs from looking abandoned — they are not a universal “anti-idle” guarantee.
People often want a tab to stay signed in, keep a queue green, or prevent a kiosk page from showing a stale idle screen. Auto Refresh Turbo reloads the tab on a schedule via the service worker and Chrome alarms. Whether that preserves your session depends on how the site handles cookies, tokens, and idle timeouts.
What reload can do
- Refresh dashboards and status pages that go stale visually
- Re-hit a URL so server-rendered boards show current data
- Run independently on multiple tabs with different intervals
Normal and hard reload both leave cookies in place; hard refresh only bypasses cache. Details: hard refresh vs normal reload.
What reload cannot promise
- Beating every idle logout policy (some timers ignore mere page loads)
- Refreshing auth tokens that only renew on explicit user actions
- Keeping WebSocket-only apps “alive” without their own heartbeat
- Bypassing captchas, MFA prompts, or security challenges
If the site requires periodic clicks inside a form, reload alone may not help — and stop-on-interaction will halt refresh when you type.
Sensible setup
- Use a dedicated tab for the session you care about
- Start with a moderate interval (2–5 minutes is a common first try for “keep fresh,” not one second)
- Prefer normal reload unless cache leaves a stale shell
- Add a daily schedule so nights pause instead of hammering the origin
- Confirm cookies survive one normal reload before you rely on the loop overnight
For ops walls specifically, see auto-refresh for dashboards. For how alarms survive a closed popup, see tab lifecycle and reload.
Random intervals
A random min–max range keeps activity less metronomic while staying inside a freshness budget. Still respect rate limits — session-keeping is not an excuse for aggressive load.
Stop-after-N and safety stops
Use stop-after-N for short supervised tests. Leave suspicious-page stop on so a challenge screen can end the loop instead of reloading forever into an error page. Stop-on-click/type protects you when the same tab is also an editor.
Multi-tab sessions
Independent sessions mean your monitoring board and your admin console do not share one timer. Track running tabs in the popup list so you do not leave forgotten reloaders on sensitive hosts.
Pairing with visual feedback
If operators need to see the next tick on a wall, enable the on-page visual timer. It syncs to the worker; it does not replace cookies or invent a keep-alive API the site lacks.
Local data
Intervals and snapshots live in local chrome.storage. Optional Umami/GlitchTip telemetry is separate from the sites you reload. Read Privacy Policy before enabling on-page tools on internal apps.
When it fails
If the site still idles out, the idle policy likely needs an in-app keep-alive or a longer server timeout — not a faster extension interval. If reload itself stops, check schedule pause vs Stop in paused vs stopped and troubleshooting.
Try it
Install Auto Refresh Turbo and validate one honest cycle with the quick start.