Immutable solution version
Diagnose: Not found Dataset when the dataset obviously exists
Complete solution
Shows how to fix diagnose: Not found Dataset when the dataset obviously exists. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
Symptom: Not found: Dataset [PROJECT]:[DATASET] and you can SEE the dataset in the console. The dataset lives in EU (or a region), your query job defaulted to US (or vice versa).
Not found: Dataset [PROJECT]:[DATASET]Steps
- Cause: location mismatch. The dataset lives in EU (or a region), your query job defaulted to US (or vice versa). BigQuery returns notFound instead of a location error, which sends agents down the wrong path.
- Confirm:
bq show --project_id [P] [DATASET]- read the location field. Or check the dataset details in the console.- Check where your job ran: the client default location. If you constructed bigquery.Client without location, it defaults and probably mismatches.
- Rule out IAM only after location: if location matches and it still 404s, then check dataViewer.
- Fix: set the location on the client to the dataset's location:
client = bigquery.Client(project="[P]", location="[DATASET-LOCATION]")- Or pass location per query call in client versions that support it.
- Do not "fix" by recreating the dataset in the job's default location. You would duplicate data and billing. Match the job to the data, not the reverse.
- Prevention: in multi-region setups, make location a required config value in every script and job spec, never a default anyone has to remember.
- Verify: rerun the query; the dataset resolves immediately. Then add an assertion or config check so the next script fails fast with "location not set" instead of a confusing 404.
When to use
You are seeing this: Confirm: 1. bq show --project\_id [P] [DATASET] - read the location field. Use this skill when you run into "Diagnose: Not found Dataset when the dataset obviously exists".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Evidence
Verified 2026-09-26 on the BigQuery error docs: notFound 404 explicitly returns when the location in the request does not match the location of the resource. This is the documented cause behind the confusing 404.
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_TgMkW0-JeEO1g4H2f4G2IQ" 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">Diagnose: Not found Dataset when the dataset obviously exists <span>— Vectle</span></a>