Forum Discussion
External Data Stream issues
Hello LeahS,
Thank you for your follow‑up.Since you're using the built-in Google Analytics (GA4) connector, the request and response handling is managed internally, so you won’t have direct control over how the API payload is structured.
The error you’re encountering typically occurs when the combination of dimensions, metrics, or query scope results in a complex response that Power Query is unable to process correctly.
You may try the following:
- Reduce the number of dimensions and metrics selected
- Limit the date range further, even if already filtered
- Avoid high-cardinality fields (e.g: page path, event name, user-level dimensions)
- Split the query into smaller queries (for example, by date ranges or metric groups)
For more information on connecting to Google Analytics data using the built‑in connector, please refer to the official documentation below:
Best regards,
Ganesh Singamshetty
Community SupportHi LeahS,
Thank you for posting your query in the Microsoft Fabric Community Forum.
The error you’re seeing ”Invalid JSON payload received. Message too deep. Max recursion depth reached” indicates that the API response returned during evaluation is too complex or deeply nested, and Power Query is unable to fully parse it. When you limit the date range, the API may still be returning a large or highly nested JSON structure, which causes validation to fail before ingestion completes.
In this scenario, the issue is source/API‑side rather than the dashboard itself. consider below points:
- Ensuring the API supports server‑side filtering (so smaller, flatter payloads are returned).
- Adjusting the API query to reduce nested objects or fields returned in the response.
- If possible, transforming or flattening the JSON before it reaches Power BI / Fabric.
Once the payload structure is simplified, the stream should be able to evaluate and proceed normally.
You may also find the following documentation helpful for monitoring stream behavior and performance: Monitor the Status and Performance of an Eventstream - Microsoft Fabric | Microsoft Learn
Thanks, Kedar_Pande @ Ritaf1983 for sharing valuable insights
Best regards,
Ganesh Singamshetty
Since the source is G4 (google analytics) how would I go about doing that? I'm using the built in API connector.
- v-ssriganesh
Hello LeahS,
Thank you for your follow‑up.Since you're using the built-in Google Analytics (GA4) connector, the request and response handling is managed internally, so you won’t have direct control over how the API payload is structured.
The error you’re encountering typically occurs when the combination of dimensions, metrics, or query scope results in a complex response that Power Query is unable to process correctly.
You may try the following:
- Reduce the number of dimensions and metrics selected
- Limit the date range further, even if already filtered
- Avoid high-cardinality fields (e.g: page path, event name, user-level dimensions)
- Split the query into smaller queries (for example, by date ranges or metric groups)
For more information on connecting to Google Analytics data using the built‑in connector, please refer to the official documentation below:
Best regards,
Ganesh Singamshetty