BigQuery: Not found: Dataset was not found in location Google Cloud / Firebase Origin: Platform & cloud Last updated 4 Nov 2026

BigQuery: Not found: Dataset my-project:analytics was not found in location EU

BigQuery looked for the dataset in the wrong location (region) or the dataset doesn't exist.

Exact message you may see Not found: Dataset was not found in locationNot found: Dataset my-project:analytics was not found in location EUNot found: Table was not found in location USnotFound: Not found: JobDataset was not found in location
Explore the map of this error Full error map →
Seen on: Google Cloud

Meaning

Datasets live in one location (US, EU, europe-west1…). Queries must run in that location and can't join datasets from different locations. Set the job location in the client or the console's query settings, and check name and project spelling.

Common causes

  • Query job running in a different location than the dataset
  • Typo in project/dataset/table
  • Dataset deleted or never created
  • Cross-location JOIN
  • Wrong default project

⚡ Quick fix

  1. Set the job location: bq query --location=EU ...
  2. Verify with bq ls -d and bq show
  3. Copy data to a dataset in the same location for joins

Detailed fix by platform

bq

  1. bq show --format=prettyjson PROJECT:DATASET | grep location

How to diagnose

  1. Location — Dataset vs job?
  2. Name — Spelled correctly?
  3. Join — Same location?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Platform & cloud. Errors that are often confused with or caused by this one (click to open):

502 Bad Gateway: failed_to_connect_to_backend — Google Cloud Load Balancing: 502 Bad Gateway — jsonPayload.statusDetails: failed_to_connect_to_backend / backend_connection_closed_before_data_sent_to_client (Google Cloud / Firebase)502 Bad Gateway: fail…API has not been used in project before or it is disabled — Google Cloud: 403 SERVICE_DISABLED — Cloud Resource Manager API has not been used in project 123456 before or it is disabled. Enable it by visiting (Google Cloud / Firebase)API has not been used…Artifact Registry: Permission artifactregistry.repositories.uploadArtifacts denied — Docker push: denied: Permission "artifactregistry.repositories.uploadArtifacts" denied on resource "projects/p/locations/l/repositories/r" (Google Cloud / Firebase)Artifact Registry: Pe…BigQuery: Access Denied: Project: User does not have bigquery.jobs.create permission — BigQuery: Access Denied: Project my-project: User does not have bigquery.jobs.create permission in project my-project (Google Cloud / Firebase)BigQuery: Access Deni…BigQuery: Quota exceeded: Your project exceeded quota for free query bytes scanned — BigQuery: Quota exceeded: Your project exceeded quota for free query bytes scanned. Consider enabling billing (Google Cloud / Firebase)BigQuery: Quota excee…BigQuery: Unrecognized name — BigQuery: Syntax error / Unrecognized name: customer_id at [3:8] (Did you mean customerId?) (Google Cloud / Firebase)BigQuery: Unrecognize…Cloud SQL: failed to connect to instance — Cloud SQL: failed to connect to `host=PROJECT:REGION:INSTANCE user=app database=db`: dial error (timeout) / Cloud SQL Auth Proxy: failed to connect to instance (Google Cloud / Firebase)Cloud SQL: failed to …Cloud SQL: too many connections — Cloud SQL: FATAL: remaining connection slots are reserved / MySQL: ERROR 1040 (08004): Too many connections (Google Cloud / Firebase)Cloud SQL: too many c…BigQuery:…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.