Solution skill
BigQuery scheduled queries: permissions, cron schedule, and exports
Complete solution
Schedule queries with bigquery.transfers.get plus bigquery.jobs.create, write results to a destination table or export to GCS. Set the schedule in cron-like syntax and monitor transfer runs. Not the full reference manual.
TL;DR: Schedule queries with bigquery.transfers.get plus bigquery.jobs.create, write results to a destination table or export to GCS. Set the schedule in cron-like syntax and monitor transfer runs. Traps: - Location: the scheduled query runs in a location; it must match the source dataset location. Cross-location scheduled queries fail. - The service account BigQuery Transfer Service uses must have all the data permissions.
The fix
- The scheduled query needs a service identity with bigquery.jobs.create (to run) and read access on source datasets plus write access on the destination dataset.
- To CREATE the schedule you need bigquery.transfers.get; to run it needs bigquery.jobs.create and dataset permissions. Destination options:
- Write to a table (append or truncate) for downstream dashboards.
- Export results to GCS (CSV/Parquet) for external consumers. Schedule syntax is cron-like; pick intervals that match data freshness needs, not "every 5 minutes just in case". Each run bills like a normal query. Traps:
- Location: the scheduled query runs in a location; it must match the source dataset location. Cross-location scheduled queries fail.
- The service account BigQuery Transfer Service uses must have all the data permissions. "It works when I run it manually" means YOUR user has them, not the scheduler identity.
- Long queries timing out: scheduled runs have limits; break huge transforms into staged queries writing intermediate tables.
- Notification: configure run notifications or monitor transfer run history; silent failures are the default if you never look. Verify: trigger a manual run first, check the destination table row count and schema, then enable the schedule and watch the first two automatic runs.
When to use this
- This covers exactly what the title says: BigQuery scheduled queries.
- You are setting this up for the first time, or auditing an existing setup.
- You want the key gotchas in one place before you start.
When not to use this
- You are doing a different workflow with BigQuery; these steps are specific to the title above.
- You need the full reference docs; this is the short path, not the manual.
Compatibility
- Not pinned to a specific version; follows current BigQuery behavior.
Evidence
Verified 2026-09-26 on the scheduled queries docs: required permissions (bigquery.transfers.get to schedule, bigquery.jobs.create to run, dataset permissions), destination options, and run monitoring.
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_HxAe5ZkVrwDCpAlATuAslw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">BigQuery scheduled queries: permissions, cron schedule, and exports <span>— Vectle</span></a>