Feast BigQuery offline store failed error "NotFound: table was not found in location US"

TL;DR

Point the source at the dataset and table that exist, in the location they actually live in, by setting the BigQuery dataset location in the offline store config to match (for example a regional dataset instead of US), because BigQuery refuses a table lookup when the query location and the dataset location differ. Start with the Feast BigQuery source config and the dataset location in the BigQuery console, work on one affected call, record, or run first, and prove the fix there before running the full set. Most cases clear once the cause named in step 2 is corrected at its source rather than retried unchanged.

Feast BigQuery offline store failed error "NotFound: table was not found in location US"

Use this when

• You see this exact message or symptom: Feast BigQuery offline store failed error "NotFound: table was not found in location US"
• One run, record, call, or object is affected and you can name it
• A retry without changing anything reproduces the same result

Not for this skill when

• The system fails with a different message and none of the signals here appear
• Nothing has failed yet and you are doing first time setup or general planning
• Every service from this vendor is down for all users, which is a vendor outage to wait out first

Steps

1. Reproduce the failure once using the Feast BigQuery source config and the dataset location in the BigQuery console, and record the time, the workspace or account, and the one item it names. Verify: you have one failing item identified, not a similar older failure
2. Inspect the fully qualified table name in the data source, the dataset location shown in BigQuery, and the location value in the offline store config. Verify: you can point to the specific value, field, segment, or state that does not match what this operation needs
3. Apply the fix at that source: Point the source at the dataset and table that exist, in the location they actually live in, by setting the BigQuery dataset location in the offline store config to match (for example a regional dataset instead of US), because BigQuery refuses a table lookup when the query location and the dataset location differ. Verify: the corrected value or setting is visible in the system itself, not only in a local file or the agent notes
4. Re-run the original operation on the single affected item first. Verify: that one item completes with no trace of the failure described above, and the online and offline values for that entity agree
5. Check the downstream result a user or the next job would see, comparing it against the source for the same item. Verify: the downstream result agrees with the source in content and in timing
6. Repeat for the full set, watch the first few items in the same log you started from, and write the root cause and the changed setting into the run notes. Verify: the full run finishes, the notes name the failure and the fix, and no earlier item regressed

Variant phrasings

Feast BigQuery offline store failed error "NotFound: table was not found in location US"

The subject-first phrasing of the same failure. The fix is the same, start at step 1 and confirm the item the log or record names.

Tool-first phrasing of this failure

The phrasing searchers use once they know which system raised it. It is the same underlying problem, not a separate bug.

Why does this keep happening after a retry

The repeat-occurrence phrasing. A retry without the step 2 and step 3 checks almost always reproduces it, because the cause sits in the input, setting, or record state, not in the attempt.

Compatibility: Feast 0.36 or later, BigQuery offline store, datasets in US, EU, or single regions.

Why it happens

Datasets created outside the console often land in a region while Feast defaults to the US multi-region. BigQuery treats a location mismatch as not found rather than as a location error, which sends people hunting for a deleted table that still exists.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstDDkuExmqgVfN3sqkjBjpg