To auto refresh a dashboard in Chrome, leave the dashboard tab open, add **Refresh Page**, and set a **Repeat** wait long enough for the board to finish loading.

This keeps one status board, queue, or metrics page current. It does not rotate a wallboard through multiple tabs or decide when the data looks stale.

## Set up the dashboard reload

1. Open the dashboard in Chrome. Sign in if it needs a session. Get it to the view you actually watch.
2. Open the Tab Automation side panel.
3. Click **New Automation** and pick the dashboard tab.
4. Add [Refresh Page](/steps/refresh-page).
5. Set [Repeat](/steps/repeat). A new automation defaults to a 30-second **Fixed** wait.
6. Click **Start**. Use **Refresh** on the automation row when you want to run the Refresh Page step before the next scheduled cycle.

The main [auto-refresh guide](/blog/auto-refresh-a-tab-in-chrome) covers Chrome's lack of a built-in timer, extension permissions, and what happens when Chrome closes.

If you have several boards open, give each one a [separate automation and wait](/blog/auto-refresh-multiple-tabs-chrome).

## Set the wait longer than the load time

A heavy dashboard can take several seconds to fetch data and paint its charts after a reload. If the next cycle starts before that work finishes, you will mostly see a loading state.

Start with the 30-second default. Lengthen the wait if the board is still loading when the next cycle begins. Shorten it only when the page finishes comfortably and the data needs a faster cadence.

The Repeat wait controls the schedule. It does not measure the dashboard's load time or guarantee that its data is readable.

## Bypass cache only when needed

A normal reload can reuse cached files. If the shell stays old, turn on **Bypass cache** on the Refresh Page step. That is `chrome.tabs.reload({ bypassCache: true })` on each cycle, the same idea as a hard refresh, on a loop.

Leave **Bypass cache** off when a normal reload shows current data. It can make the page download resources again, and it does not fix a dashboard whose server is returning old data.

For a single cache-bypassing reload, use Chrome's hard-refresh shortcut instead of starting a recurring automation.

## Reloading is not monitoring

A timer-only graph does not read metrics or compare the page with an earlier version. You still inspect the board yourself.

If a particular status should trigger a desktop notification, add [If / Else](/steps/if-else) to check it and [Send Alert](/steps/send-alert) in the branch that should notify. If the page updates after it loads, [Wait Until](/steps/wait-delay) can poll for that later change. The [auto refresh vs page monitor guide](/blog/auto-refresh-vs-page-monitor) distinguishes those choices.

## Dashboard reload versus a tab carousel

A dashboard reload keeps the same tab selected and reloads its page. A tab carousel changes which tab is displayed.

Tab Automation handles the first job. It does not cycle tabs, hide browser controls, or provide kiosk mode. If the dashboard sits behind another tab while you work, see [auto refresh a background tab in Chrome](/blog/auto-refresh-background-tab-chrome).