Schedule a report when you want a fresh result at a regular time, such as a Monday morning check of customer growth or a daily review of content performance. Use run history to see whether it finished, read earlier results, and investigate failures.
A schedule controls when the report runs. It does not change the reporting period inside the result or set up email delivery. Open Reports to read the output.
Check the report before scheduling it
Open the report and read its latest result. If it has never run, select Run now and wait for it to finish. Check the measures, source data, and period labels before making it recurring.
For a new report, see Creating a custom report. A schedule will repeat the saved report; it will not add missing calculations or connect new sources.
The report must be active to run. If it is paused, choose Edit report, turn on Report is active, and select Save changes. Archived reports cannot run.
Changing a schedule requires settings write access. You may be able to read or run a report without being able to edit its schedule. If the controls are unavailable, ask your site owner to review your feature and settings access.
Set a recurring schedule
- Open Reports and select the report you want to schedule.
- In its Schedule card, select Set a schedule, or Change if it already has one. You can also use Change schedule in Report actions.
- Choose a Cadence. For daily, weekly, or monthly runs, set the Time and any day selection shown.
- Check Timezone and the First run preview. Make sure the first occurrence is the one you intend.
- Select Save schedule. Confirm that the report's Schedule card reflects the change.
The available cadences are Every day, Every week, Every month, Every hour, Every 30 minutes, and Custom cron.
For a weekly report, choose Day of week. For a monthly report, choose Day of month. Days past the 28th are skipped in shorter months. A report scheduled for the 31st does not automatically move to the last day of a month that has fewer days. Choose a date from 1 to 28 if you want a run in every month.
Hourly runs are scheduled at the top of the hour. Every 30 minutes uses the hour and half-hour marks; it does not mean 30 minutes after you saved the schedule.
When changing a schedule inside the report editor, finish by saving the report too. The schedule dialog there updates your pending edits. Select Save changes, Create and run, or Create report, as appropriate, to save the report and its schedule. The dialog opened directly from a saved report's detail page saves the schedule when you select Save schedule.
Check the timezone and first occurrence
The selected Timezone determines the clock used for the schedule. The First run preview is shown in your own local time. Those times can look different while referring to the same moment.
For example, choose the team's timezone for a Monday morning report, then use the preview to check when that occurrence falls where you are. Do not change the scheduled hour just to make the local preview display the same number.
Review schedules around daylight-saving changes if the exact timing matters. Use History to confirm what actually ran; a preview is an expected occurrence, not proof of completion. Processing may start after the scheduled time.
Use Custom cron only when the preset cadences do not fit. Enter a five-field Cron expression in this order: minute, hour, day of month, month, day of week. For example, 0 9 * * 1 schedules Monday at 09:00 in the selected timezone.
Prefer a preset for ordinary daily, weekly, and monthly schedules. If Cedros cannot read the expression or shows an error when saving, correct it before relying on the schedule. An absent first-run preview is a reason to recheck the expression and timezone.
Change or stop recurring runs
To change a recurrence, reopen Change schedule, adjust the fields, and select Save schedule. Check the updated Schedule card afterward.
To return an active report to manual use, open the schedule dialog and select Clear schedule. From the saved report's detail page, this applies immediately. From inside the report editor, finish saving the report. Clearing the schedule removes its recurrence; you can still use Run now while the report is active.
To pause both scheduled and manual runs, choose Edit report, turn off Report is active, and select Save changes. The report keeps its saved schedule. Review that schedule before turning the report back on.
Changing or clearing a schedule does not erase earlier results. It also should not be treated as a way to cancel work already queued or running. Check the run's status separately.
Find and compare earlier results
- Open a report and find its Runs list to review that report's history. For runs across reports, return to Reports and select History.
- In History, use All statuses to narrow the list to Queued, Running, Succeeded, or Failed. Use All triggers to select Manual, Scheduled, or Assistant.
- Review the report name, status, started time, duration, and outcome. Use the pagination controls to reach older runs.
- Select a run to open its result on the report's page. Check the timestamp so you know which result you are reading.
- Select View latest when you want to return from an earlier run to the latest result.
Clear filters restores the unfiltered history list. An empty filtered list does not mean the report has never run; try clearing the filters or opening its own Runs list.
The trigger tells you how the run began. Manual means it was requested directly, Scheduled means it came from a recurrence, and Assistant means it was requested through the assistant. It is separate from the outcome.
An earlier run stays selected even when a newer run arrives. This lets you keep reading the result you opened. To compare two runs, open their links in separate tabs and check both timestamps and reporting periods.
Past results show what those runs returned. A new run uses the report's current setup and available data; it is not a replay of an older result. Changes in totals can reflect a different reporting window, new records, or a changed report definition. For visitor metrics, Understanding your site analytics explains the measures and date windows.
Read status and output together
Queued means the run is waiting to execute. Running means it is being processed. Neither is a finished result. Some temporary failures may return a run to the queue for another attempt.
Succeeded means execution finished. Read the result to decide whether it answers your question: a completed run can still contain sparse data, an empty summary, or a narrower set of measures than you expected.
Failed means the run did not complete successfully. Open it and read What went wrong. The history row may also show an error in its outcome.
Expand Operational details when you need the Scheduled, Started, and Finished times or the Run ID. For scheduled runs, Scheduled is the intended recurrence time. Started is recorded when the run enters the queue, so the elapsed duration can include waiting and retries. Use Copy ID when asking for help with a specific run.
Expand Raw report data for the saved output and use Copy if you need to inspect it elsewhere. It may contain customer or business information, so share it only with people who should have access. The current report's What this report reads section describes its saved setup; use the selected run's output and timestamp when investigating an earlier result.
Troubleshoot missed or failed runs
The next run did not appear. Confirm that the report is active, the schedule saved, and the timezone and day are correct. For monthly schedules, check whether the selected date exists in that month. Clear History filters before concluding there is no run.
A run is still queued or running. Open that run and check its status again before requesting another one. Do not repeatedly select Run now to try to speed it up. If it remains stuck, give the site owner the report name, run ID, and relevant timestamps.
The run failed. Read the error, correct the named problem, then use Run now when the report is ready. This creates a new run rather than replacing the failed history entry. Re-running without fixing a persistent problem may produce the same failure.
History says it could not load. Select Try again. A loading error does not establish that there are no runs. If it persists, check access and ask the site owner for help.
The result is missing expected activity. Check the report's sources and period before changing the schedule. For collection settings, see Configuring analytics and tracking integrations. Running more often does not recover events that were never collected.
The schedule could not be saved. Read the error and recheck the fields. If you were creating a report, the report itself may already have saved. Open it and correct its schedule instead of creating a duplicate.