KEY POINTS
Key points
- Note the full error message first, and check whether it affects one chart, the whole report, or particular viewers.
- For access and data source problems, check that accounts, credentials and sources are still valid before reconnecting anything.
- “Invalid combination of metrics and dimensions” means checking field compatibility; for GA4, use Google’s Dimensions & Metrics Explorer.
- GA4 quota problems are handled by reducing query use. Caching, extracts and BigQuery each have their own conditions and are not interchangeable.
A report breaks: what is the first step?
Confirm the error message and its scope first, then decide whether to check access, data sources or the chart itself.
Charts turning into grey boxes can have very different causes. Some are temporary system issues, some are viewers lacking authorisation, and some are a calculated field that no longer works.
Before changing anything, write down the full message and check three things: whether others see the same problem, whether other charts work, and whether permissions or data fields changed recently.
Six areas to check
Based on Google’s troubleshooting guide, the table below groups errors into six areas to check. This grouping is ours for diagnosis; one error can involve more than one layer.

| Area | Common messages or symptoms | Possible causes | What to do first |
|---|---|---|---|
| System and network | System error; the page stops responding. | Temporary service, network or browser issues. | Refresh or try again later; if it persists, compare other browsers, cache and extensions. |
| Access | No access to Data Studio. | The viewer’s organisation has not enabled the service, or report sharing permissions are insufficient. | Check the signed-in account and sharing settings. If the organisation has not enabled the service, the viewer’s own company admin has to handle it. |
| Data sources and credentials | Missing data source; data set configuration error; can’t access data set; underlying data changed. | Credentials or underlying access changed, the data source was deleted, or the field structure changed. | Confirm the source and authorisation are valid, then refresh fields, reconnect, or replace the broken data source as the message indicates. |
| Chart configuration | Chart configuration incomplete; invalid combination of metrics and dimensions. | Required fields missing, incompatible fields, or a formula error. | Check chart settings and calculated fields; start with fewer dimensions and metrics to find a combination that works. |
| Blending | Join configuration incomplete; table missing a data source. | Join conditions or key fields missing, or one source has broken. | Check each source and the conditions and key fields the chosen join type needs. |
| GA4 quota | This resource has made too many requests in the past hour, or other quota messages. | A GA4 Data API quota of some kind has been exceeded. | Review token and query use, identify the type of limit, reduce repeat queries and wait for that quota to recover. |
What does “invalid combination of metrics and dimensions” mean?
A data source supports only certain field combinations; a dimension and a metric existing separately does not mean they can share a chart.
When this message appears, keep only the most basic fields, then add other dimensions, metrics or calculated fields back one at a time to find which one triggers the problem.
For GA4 reports, check field compatibility first in Google’s Dimensions & Metrics Explorer. For custom calculated fields, also check the formula, data type and aggregation.
For the basics of dimensions and metrics, see Fixing broken charts: dimensions versus metrics (in Chinese).
Out of GA4 quota: what can be done?
First find which charts query GA4 directly, then choose a way to cut queries that fits how fresh the data needs to be.
In edit mode, right-click the canvas or a chart and choose “Google Analytics token usage” to see how tokens are being used. According to Google, a green checkmark means the chart loaded from memory without consuming tokens; a red X means it queried GA4 directly. The red mark on its own does not mean the chart has an error.
Ways to cut GA4 queries
Then work through these options according to how the report is used.
- Share the cache, where authorisation allows. If all viewers should see the same data scope, consider owner’s credentials. If queries need to follow each person’s underlying access, do not switch to a shared credential just to save quota.
- Reduce duplicate data sources and queries. Consolidate GA4 data sources with the same purpose into one reusable source, remove unnecessary duplicate charts, and check query date ranges and complexity.
- Check how much the report is used. A report embedded on a high-traffic page can add heavy query load. Consider whether it needs live queries at all, or whether the data could be provided another way.
- When data does not need to be live, consider an extract. An extract creates a snapshot that later report views read from; creating or refreshing it still queries the source. If GA4 quota is already exhausted, wait for that quota to recover before the extract can run. Google’s guide notes the wait can be up to 24 hours depending on the limit hit; not every quota takes a fixed 24 hours, and running an extract does not reset quota.
- When a different query setup is needed, consider BigQuery. Exporting GA4 data to BigQuery and using the BigQuery connector changes how the report calls the GA4 Data API. It does require planning the export, query permissions, data model and cost management, and checking how the metrics differ from those in the GA4 interface.
- Consider Analytics 360 or other connectors based on overall needs. Analytics 360 has higher quotas; for third-party connectors, check how they actually fetch data, their limits and costs, and do not assume a new connector escapes quota limits.
Which approach fits
GA4 has several types of quota that recover in different ways; go by the actual error and Google’s quota documentation.
For lightly used internal reports, start with caching and duplicate queries and see whether things improve. For reports with many viewers or a fixed refresh schedule, it is worth looking further at snapshots and how data is supplied. For more detailed steps, see Troubleshooting: avoiding the GA4 quota trap (in Chinese).
Frequently asked questions
Most diagnosis can first be narrowed to a specific account, source or chart, then the matching setting adjusted.
The report works for me but breaks for others. Why?
The viewer may lack access to the underlying data, or the sharing settings, signed-in account or the other organisation’s service policy may differ. Compare the error messages and check which credential type is in use before widening any access.
Refreshing didn’t help. Does the report need rebuilding?
Not necessarily. If the problem is confirmed to be with the data source, create a new data source and test it on a small scale; once the connection and fields work, replace the source on the affected components. Afterwards, check calculated fields, filters and chart settings.
The report won’t save, or some features don’t respond. What now?
Conflicting browser extensions are one possible cause Google lists. Try another browser, or disable extensions one at a time to see whether the problem goes away. If not, look into other causes based on the actual error.
Will switching to BigQuery make the numbers match GA4 exactly?
Not necessarily. BigQuery event data and the GA4 interface may use different processing and metric definitions. Before switching data sources, confirm the metrics, date ranges and calculation logic being compared; similar field names do not mean the results should match.
When a report breaks, keeping the message, confirming the scope and testing one possible cause at a time usually finds the problem more easily than changing several settings at once. If the same error keeps coming back, review the data sources, permission setup and query approach, and record the results of each change. For help working out what is wrong with existing reports, get in touch.
Further reading
References
- Google Cloud, Data Studio troubleshooting guide.
- Google Cloud, Data credentials.
- Google Analytics, GA4 Data API quotas.
- Google Analytics, Dimensions & Metrics Explorer.



