I’m experiencing an issue when trying to open BigQuery Public Datasets from the Google Cloud Console.
The problem does not appear to be related to permissions or IAM because I can successfully query the datasets using the BigQuery CLI (bq).
The error only occurs when the Console tries to open the dataset using the internal add-data(cameo:product) route.
Environment
- Google Cloud Project: (PII Removed by Staff)
- BigQuery API: Enabled
- Account: Google Workspace / Gmail account
- Browser: Google Chrome (latest version)
- Operating System: Windows 11
- Region: Brazil
URLs
The following URLs work correctly:
Documentation
https://docs.cloud.google.com/bigquery/public-data
Marketplace
https://console.cloud.google.com/marketplace/browse?filter=solution-type:dataset
Dataset page
https://console.cloud.google.com/bigquery?p=bigquery-public-data&d=un_sdg&page=dataset&project=(PII Removed by Staff)
However, when the Console redirects to:
https://console.cloud.google.com/bigquery/add-data(cameo:product/...)
the page fails to load.
Error
The Console displays:
Failed to load.
An error occurred while loading:
`/bigquery/add-data(cameo:product/bigquery-public-data/google-books-ngrams-2020)?project=(PII Removed by Staff)
The same behavior happens with multiple public datasets, not only one specific dataset.
What I already verified
BigQuery API is enabled.
*
Account authentication is correct.
*
Project is correctly selected.
bqCLI works normally.- I can query public datasets successfully.
Example:
SELECT COUNT(*)
FROM `bigquery-public-data.un_sdg.indicators`
Using the CLI:
bq query --use_legacy_sql=false \
'SELECT COUNT(*) FROM `bigquery-public-data.un_sdg.indicators`'
returns:
1050781
Therefore, BigQuery itself is working.
Troubleshooting already attempted
- Incognito mode
- Browser cache cleared
- Different browsers
- Different public datasets
- Verified IAM permissions
- Verified enabled APIs
The issue persists only when opening datasets through the add-data(cameo:product) route.
Question
Has anyone experienced this recently?
Is this a known issue with the current Google Cloud Console UI, or is there any workaround besides querying the datasets directly?

