Use Repeat to run the graph again after an optional wait, stop after a chosen cycle count, or stop after a duration. It is the End block, not an Add Step, and it never reloads the tab.
When Repeat is on, you choose unlimited cycles or a count, and a wait: No wait, Fixed, or Random range. The wait stepper is seconds only, 0–3600. No wait or a 0-second setting requests the next cycle without an added pacing delay, but Chrome still schedules the alarm. It does not guarantee an immediate next cycle.
Stop after a duration is optional and off by default. Turn it on to run for a set time: hours 0–24 and minutes 0–59, at least 1 minute, default 1 hour. Before Run, the End block shows Stops after Run plus that duration. After Run it shows Stops at … for the run’s deadline. When Chrome delivers the deadline alarm, the run stops without waiting for the current cycle to finish. Alarm delays and device sleep can postpone that stop. If you also set a cycle count, the run stops at whichever comes first. Unlimited cycles plus a duration is “run for 2 hours,” not “until you pause.”
Repeat is off in a new automation, so it runs once. Turning Repeat on uses unlimited cycles, no duration, and a 30-second Fixed wait.
Repeat uses extension alarms. Chrome limits alarms in installed extensions to at most once every 30 seconds and can delay them further, including alarms requested with a shorter delay. Unpacked development builds are exempt. The wait is a requested gap between completed cycles, not a guaranteed reload frequency.
A timer-style reload is Refresh Page plus this wait. On a For Each Link walk, the card’s “every 5s” is this wait between complete passes — not time spent on each link.
Each cycle and When it stops alerts stay off until you enable them here. Each can fire desktop, sound, and webhook — Slack, Discord, ntfy, or any HTTPS endpoint — using this automation’s selected destinations. A duration complete is a stop event with reason completed. On the last cycle, if both switches are on, Chrome sends a cycle webhook and then a completed-stop webhook. In-flow banners are Send Alert.
Timers do not fire after you quit Chrome. If a duration deadline passed while the browser was closed, the run completes when Chrome starts again or when you Resume.
How to set it
Open the graph. The End block is always there. Leave Repeat off for one cycle, or turn it on for repeated runs. Change the wait if 30 seconds is wrong. Match a dashboard wait to load time so the board can paint. Turn on Stop after a duration when you want the automation to finish on its own instead of running until you pause.
Limits and related controls
A repeated reload needs a Refresh Page step. To wait on each URL in a link loop, put Wait / Delay inside Each Link. Repeat waits between cycles; it cannot start at a clock time.
Related guides
How to auto refresh a tab in Chrome is Refresh Page plus Repeat. Reload until text appears uses When it stops after a successful Until pause. The side panel tour shows the End block defaults.