Skip to main content

Scheduling Queries

A schedule runs a query automatically at set times and can email the results to a list of recipients. This turns any query into an automated report — a daily sales summary, a weekly KPI digest, or an hourly health check.

Creating a schedule​

On a saved query, add a schedule by specifying:

  • When it runs — the timing of the automatic execution.
  • Recipients — the email addresses that should receive the result.
  • Parameters — values for any form variables the query needs, so the scheduled run is fully self-contained.
  • Email row cap — how many result rows to include in the email (defaults to 25; see The emailed result).

A query can have more than one schedule, which is handy when different recipients need the same report at different cadences.

The emailed result​

When a scheduled query runs, Kvery emails the result as a table. To keep messages readable, the emailed table has a row cap — 25 rows by default, which you can change per schedule (0–999) when you create or edit it. For larger result sets, consider:

  • adding a LIMIT or aggregating the data in the query itself, or
  • emailing a summary and linking recipients to the full shared query or dashboard.

Monitoring scheduled runs​

Every scheduled execution is recorded in the logs with its response code. If a scheduled query starts failing — for example after a schema change — the log shows the error so you can fix it quickly. Filter the logs by response code to find failures fast.

Removing a schedule​

Delete a schedule when it is no longer needed. The query itself is unaffected and can still be run manually or via its API.

Tips​

  • Schedules run server-side and do not require you to be logged in.
  • Because schedules run in the background, they are a good fit for heavier queries that you would not want to wait on interactively.
  • Combine scheduling with history: if a scheduled report breaks after an edit, roll the query back and the next run is healthy again.