View and Dictionary popups carry a short built-in guide to their refresh schedule. Open it while you fill in Refresh Settings, when you want to check what the interval, the offset or the retries do. The window is titled Refresh Settings, and its subtitle reads "How the refresh schedule is built".
The timeline draws one schedule as a picture:
The diagram's description reads: "Timeline: the offset shifts the first refresh away from the period boundary, then the interval sets the spacing between refreshes."
Below the timeline, four cards explain the fields of Refresh Settings:
The footer of the guide adds a hint: "Offset the run so it lands after your source sync finishes."
The guide explains the schedule only. The fields and the controls that run the refresh live with the object: see Views and the Dictionary General step.
In a View or Dictionary popup, on its General step. The book icon sits beside the Refresh Settings title, and its tooltip reads Refresh settings guide. Click it to open the window, and Got it to close it.
The four cards cover Refresh Interval + Unit, Refresh Offset + Unit, Retries and Where it runs. The timeline above them shows the offset and the interval on one schedule.
The offset shifts the first refresh away from the period boundary, and the interval sets the spacing between refreshes. The timeline is labelled offset and interval, and its description reads: "Timeline: the offset shifts the first refresh away from the period boundary, then the interval sets the spacing between refreshes."
It shifts the run inside its period, so a daily refresh lands at 03:00 instead of midnight. The offset is optional, and None clears it.
Empty uses ClickHouse's default of 2, so a failed refresh is retried twice. Enter -1 to retry indefinitely.
So the run does not start before your source has finished syncing. The footer of the guide reads: "Offset the run so it lands after your source sync finishes."
No. The Where it runs card reads: "These fields become the refresh clause on the materialized view itself, with no separate scheduler in between."