Skip to content

Weekly schedule ​

A weekly schedule runs the report on selected days of the week at a set time. Well suited for weekly reporting and planning.

How it works ​

  • The run happens on the selected days of the week at the specified time
  • You can select one or several days (Mon, Tue, Wed, Thu, Fri, Sat, Sun)
  • Example: Mon + Thu at 09:00 — runs twice a week

Step-by-step instructions ​

1. Open the schedule settings ​

In the builder or on the report page, go to the Schedule section.

2. Choose the frequency ​

Select Weekly from the dropdown.

3. Choose the days of the week ​

Check the boxes for the days you need:

  • Monday — typical for weekly reports (data for the past week)
  • Mon + Wed + Fri — three times a week for operational monitoring
  • Mon-Fri — every business day
  • All 7 days — equivalent to a daily schedule

4. Set the run time ​

Set a time in HH:MM format. Recommendations: for weekly reports (Monday) — 08:00-10:00, since last week's data is guaranteed to be ready. For midweek runs (Wednesday, Friday) — similar to daily, 08:00-10:00.

5. Configure the timezone ​

Set the timezone. This is especially important for distributed teams: Monday in UTC+3 arrives earlier than in UTC-8.

6. Configure missed-run behavior ​

Standard options: skip or catch up.

7. Enable and save ​

Turn on the toggle and click Save.

Specifics ​

  • Frequency: 1 to 7 runs per week
  • Run time: the same for all selected days
  • Recommended write mode: Replace (full snapshot for the week), Append (weekly snapshots)
  • Recommended date range: last_7d for weekly overviews, yesterday for operational reports

Example configurations ​

ScenarioDaysTimeDate rangeMode
Weekly reportMon09:00last_7dReplace
Monitoring 3x a weekMon, Wed, Fri08:00yesterdayAppendDedup
Daily on weekdaysMon-Fri08:00yesterdayAppend
Sunday digestSun18:00last_7dReplace

When to use it ​

  • Weekly reporting for clients or leadership
  • Monday snapshots of data
  • Operational monitoring several times a week
  • Reports that aren't needed daily
  • Daily — a more frequent run
  • Hourly — for operational monitoring
  • Timezone — how timezone affects the days of the week
  • Missed runs — behavior when a run is missed

Maintained by the LightLead Documentation Team · Last verified: 2026-07-25