Schedule a BigQuery or Databricks query.

Any query that runs once by hand can run itself. This tutorial covers a BigQuery or Databricks source specifically, because both are now among the connections the background helper can run with QueryFlow closed, not just while the app is open.

Before you start

• A working connection and a query. File and email output are in Studio. S3, SFTP, databases and the rest need Pipelines.

Steps

1. Write or open your query in the SQL Editor.
2. Click Schedule in the toolbar.
3. Pick a Trigger Type: Manual, Interval, Daily, Weekly or Custom Cron, and set the time.
4. Choose where results go: No Output, Save to File, Email, or on Pipelines SFTP, Amazon S3, Database, Google Sheets, Slack or Microsoft Teams.
5. Turn on Enable immediately and click Create Job.
6. To run jobs with QueryFlow closed, open Settings → Scheduling and turn on Run Jobs When App Is Closed.

With that toggle on, the background helper runs Snowflake, Redshift (IAM keys), BigQuery and Databricks jobs that deliver to S3, SFTP, a local file or email. Other jobs run while QueryFlow is open.

Be precise about the 100,000-row limit per query and the 25 MB Databricks result cap: a scheduled job that would exceed either doesn't get a partial result, it fails, so add a LIMIT or narrow the columns up front rather than after the first failed run.

The Trigger Type you pick shapes how you should think about the job. Interval is for anything that just needs to happen regularly regardless of the clock, Daily and Weekly are for report-style jobs tied to a specific time, and Custom Cron is there for the schedule that doesn't fit either, like every weekday at 6:45 AM but never on the last business day of the month.

Run Jobs When App Is Closed is the setting that decides whether a job actually fires while you're at lunch or asleep. Turn it on once, in Settings, Scheduling, and macOS will ask you to approve a background helper the first time it tries to launch. That approval step is a macOS security prompt, not a QueryFlow one, and it only needs to happen once per Mac.

Worth being exact about what the helper can and can't do: it runs Snowflake, Redshift with IAM keys, BigQuery and Databricks jobs, and only when they're delivering to S3, SFTP, a local file or email. A job with any other source or destination, Google Sheets or Slack for example, still runs, but only while QueryFlow itself is open. If a job silently stops firing after you close the app, that combination is usually why.

If something goes wrong

Related

See Studio and Pipelines pricing.