Scheduled queries
Run a query on a schedule and do something with the result.
Data Warehouse → Scheduled runs a query on a schedule and does something with the output.
Configuring
| Field | Notes |
|---|---|
| Query | Saved or inline |
| Connection | |
| Schedule | Interval in minutes |
| Export CSV | Attach the result |
| Channels | Where it goes |
What it is for
| Use | Example |
|---|---|
| A recurring extract | Yesterday's settlements to the finance channel |
| A regular check with a human reader | Weekly top-error report |
| Feeding something else | A CSV another system picks up |
Scheduled query or alert?
| Question | Answer |
|---|---|
| Should somebody be told only when a number is wrong? | SQL alert |
| Should somebody see the numbers every time? | Scheduled query |
A scheduled query that people learn to skim is not monitoring, and turning one into an alert is usually a one-line change. If you find yourself scanning a daily export for a number being out of range, that is a threshold — write it down as one.
Runs
Each run records when, how long it took, how many rows, and any error. A run that fails is visible rather than silently missing.
Cost
Scheduled queries appear in the cost monitor with their frequency and duration. A five-minute schedule on an expensive query is 288 executions a day and is usually not deliberate.
Where this behaviour lives: backend/internal/service/dwh_advanced_svc.go, frontend/src/app/dwh/scheduled/. If the code and this page disagree, the code is right — please fix the page.
Part of Data warehouse — Querying the warehouse, and alerting on what the query returns.