What causes Fabric Pipeline Error 2001?

The external web endpoint called by the Web activity returns a large response body that exceeds 4 MB. The pipeline is using a Web activity to retrieve bulk data that should instead be handled by a dedicated copy or data flow activity. Query parameters or filters on the web request are too broad, causing the API to return an unfiltered large dataset. Chained Web activity outputs are being aggregated and passed forward, compounding payload size

How do I fix Fabric Pipeline Error 2001?

Step 1: Inspect the web endpoint being called and measure the actual response size; use tools like Postman or curl to evaluate the payload.. Step 2: Add filtering, pagination, or query parameters to the web request to reduce the size of the response payload below 4 MB.. Step 3: If the web endpoint returns large datasets, replace the Web activity with a Copy activity or Dataflow activity that is designed for high-volume data movement.. Step 4: If only a subset of the response is needed downstream, consider server-side filtering at the API level or use a serverless function to pre-process and trim the response before returning it to the pipeline.. Step 5: Re-run the pipeline after adjustments and verify the Web activity output stays within the 4 MB limit.

High severitycapacityMicrosoft Fabric →

Power BI Refresh Error:
Fabric Pipeline Error 2001

What does this error mean?

The response payload returned by a Web activity exceeds the maximum supported output size of approximately 4 MB. The pipeline cannot process or pass the oversized output to downstream activities.

Common causes

1The external web endpoint called by the Web activity returns a large response body that exceeds 4 MB
2The pipeline is using a Web activity to retrieve bulk data that should instead be handled by a dedicated copy or data flow activity
3Query parameters or filters on the web request are too broad, causing the API to return an unfiltered large dataset
4Chained Web activity outputs are being aggregated and passed forward, compounding payload size

How to fix it

1Step 1: Inspect the web endpoint being called and measure the actual response size; use tools like Postman or curl to evaluate the payload.
2Step 2: Add filtering, pagination, or query parameters to the web request to reduce the size of the response payload below 4 MB.
3Step 3: If the web endpoint returns large datasets, replace the Web activity with a Copy activity or Dataflow activity that is designed for high-volume data movement.
4Step 4: If only a subset of the response is needed downstream, consider server-side filtering at the API level or use a serverless function to pre-process and trim the response before returning it to the pipeline.
5Step 5: Re-run the pipeline after adjustments and verify the Web activity output stays within the 4 MB limit.

Frequently asked questions

Can I increase the 4 MB output limit for Web activities?

No, the 4 MB limit is a platform-enforced constraint on Web activity output in both Fabric Data Factory and Azure Data Factory. The recommended approach is to reduce response size or use a different activity type for large data volumes.

What activity should I use instead of Web activity for large data transfers?

Use the Copy activity for moving large datasets between supported connectors, or use a Dataflow activity for transformation-heavy scenarios. Web activity is intended for lightweight HTTP calls such as triggering webhooks or retrieving small metadata payloads.