logo
search
Others

Fix Microsoft Fabric Dataflow Error When BigQuery Tables Are Hidden

Maira MehtabMaira Mehtab Sep 20, 2026 869 views

Question details

The user is experiencing a dataflow failure when connecting Microsoft Fabric Gen1 to Google BigQuery.

Product
Microsoft Fabric
Device & OS
not provided
Scenario
Running or refreshing a dataflow that connects to Google BigQuery where some tables are hidden or have loading disabled.
Observed behavior
The dataflow fails and throws a Storage API 'Stream removed' error.
Before you start

Ensure you have workspace administrator permissions in Microsoft Fabric and the necessary viewer roles in your Google BigQuery project to access refresh logs and table configurations.

Solution 1Recommended

Consult the Microsoft Fabric Community

Because this is a specific backend integration and Storage API issue, escalating it to Microsoft Fabric experts is the most effective way to find a workaround.

The 'Stream removed' error often indicates an unexpected interruption in the data stream between the BigQuery Storage API and Microsoft Fabric. When tables are hidden or have loading disabled, metadata mismatches can trigger this failure. Engaging with the specialized community helps Microsoft engineers track and address this specific bug.

1
Gather your configuration details

Document your dataflow setup, focusing on the queries that connect to Google BigQuery and the specific settings applied to the hidden or disabled-loading tables.

2
Collect the error logs

Navigate to the refresh history of your dataflow and copy the complete error details, specifically the Storage API 'Stream removed' message.

3
Post in the community forums

Visit the official Microsoft Fabric Community support page and create a new post detailing your issue. Make sure to omit any sensitive business data or credentials from your screenshots and logs.

Protect your data: Always sanitize your logs and configuration screenshots to remove any proprietary table names, project IDs, or authentication tokens before posting publicly.
Free Microsoft Office alternative

Analyze Your Exported BigQuery Data with WPS Office

While troubleshooting complex Microsoft Fabric dataflow connections, you may need to manually export and analyze your BigQuery data. WPS Office is a free, lightweight, and highly compatible alternative to Microsoft Office, making it easy to open large CSV exports and Excel files without expensive subscriptions.

  1. 1. Export data from BigQuery: Run your query in the Google Cloud Console and select the option to export the results as a CSV file to your local drive.
  2. 2. Open with WPS Spreadsheet: Launch WPS Office, select 'Spreadsheet', and open your downloaded CSV file.
  3. 3. Analyze your data: Use WPS Spreadsheet's built-in data tools to format, filter, and create pivot tables from your dataset.
Fully compatible with Microsoft Excel (.xlsx) and CSV formatsLightweight architecture ensures fast loading of large data extractsIncludes advanced data analysis tools like PivotTables, filters, and chartsFamiliar user interface makes transitioning seamless and intuitive
microsoft office alternative - wps office

Frequently Asked Questions

What does the 'Stream removed' error mean in Google BigQuery?

This error generally occurs when the BigQuery Storage API abruptly terminates a data stream. In the context of Fabric, it can happen if the metadata for hidden tables causes the connector to read invalid or unexpected schema states.

How do I disable load for a table in Microsoft Fabric dataflow?

Open your dataflow in Power Query Online, right-click the specific query or table on the left panel, and uncheck the 'Enable load' option. This keeps the query available for transformations but prevents it from loading into the final destination.

Where can I find the refresh history for my dataflow?

Go to your Microsoft Fabric workspace, locate your dataflow item, click the ellipsis (...) next to its name, and select 'Refresh history'. This will display a list of all successful and failed runs along with detailed error logs.