Skip to content

Scheduling

Automate your data quality checks by scheduling profiling runs, test runs, and monitor runs to recur on a regular basis.

Create a schedule

Where you create a schedule depends on the operation:

  • Profiling — Click Schedules on the Table Groups or Profiling Runs page.
  • Test runs — Click Schedules on the Test Suites or Test Runs page.
  • Monitors — Click the (settings icon) on the Monitors page. The monitor schedule is configured as part of Monitor Settings.

Set the frequency

The schedule picker offers preset frequency options so you don't need to write cron expressions for common patterns:

  • Every x hours — Run at a fixed interval (e.g., every 4 hours starting at midnight).
  • Every x days — Run at a specific time on a recurring day interval.
  • On certain days — Pick specific days of the week and a time (e.g., Monday and Thursday at 6:00 AM).
  • Custom — Enter a cron expression directly for more complex schedules. See Common cron expressions below.

Select a timezone, then choose a frequency. The dialog shows upcoming run times so you can verify the schedule before saving.

Note

Monitor schedules only support the Every x hours and Every x days presets.

(Schedule management dialog)

Manage existing schedules

Open the same schedule dialog to view, pause, resume, or delete existing schedules. Pausing a schedule temporarily stops it from triggering without deleting the configuration.

Operation Frequency Rationale
Profiling Biweekly to monthly Profiling is resource-intensive and the characteristics it measures change slowly.
Test runs Daily to weekly Tests validate data content rules. Running daily catches issues soon after they are introduced.
Monitors ~2x the expected data change frequency Run monitors at roughly twice the frequency your tables change. For example, if tables update daily, run monitors every 12 hours. This gives the prediction model meaningful data points — running too frequently on slow-changing data can teach the model a false constant pattern.

Tip

Schedule profiling and test runs to occur after your data pipelines complete, so they evaluate fresh data. For monitors, stagger the schedule relative to expected pipeline completion times.

Reference

Common cron expressions

If the presets don't cover your use case, select Custom and enter a cron expression:

Expression Description
0 0 * * * Every day at midnight
30 3 * * 1-5 Every weekday at 3:30 AM
0 6 1,15 * * 1st and 15th of each month at 6:00 AM