What causes Fabric Pipeline Error 2002?

Large inline JSON bodies or dynamic content expressions are being passed directly in the Web activity request body configuration. Activity configurations reference large parameter values or pipeline variables that inflate the total payload size. Chained outputs from previous activities are being embedded directly into the Web activity body rather than passed by reference. Multiple large configurations are stacked within a single Web activity instead of being split across multiple activities

How do I fix Fabric Pipeline Error 2002?

Step 1: Review the Web activity configuration and identify all inline content, dynamic expressions, and referenced pipeline variables contributing to payload size.. Step 2: Move large request body content out of inline configuration and into external storage (e.g., Azure Blob Storage or Azure Key Vault) and retrieve it via a separate lookup or variable before the Web activity.. Step 3: Break complex Web activity configurations into smaller, sequential activities where possible to reduce per-activity payload.. Step 4: Minimize the use of large dynamic content expressions in the request body; pass only essential parameters rather than full dataset outputs.. Step 5: Re-run the pipeline and verify all activity payload sizes are within the supported limits.

High severitycapacityMicrosoft Fabric →

Power BI Refresh Error:
Fabric Pipeline Error 2002

What does this error mean?

The total payload size of a Web activity — including activity configurations and inputs — exceeds the platform's enforced size limit. The pipeline cannot execute the activity with the current configuration.

Common causes

1Large inline JSON bodies or dynamic content expressions are being passed directly in the Web activity request body configuration
2Activity configurations reference large parameter values or pipeline variables that inflate the total payload size
3Chained outputs from previous activities are being embedded directly into the Web activity body rather than passed by reference
4Multiple large configurations are stacked within a single Web activity instead of being split across multiple activities

How to fix it

1Step 1: Review the Web activity configuration and identify all inline content, dynamic expressions, and referenced pipeline variables contributing to payload size.
2Step 2: Move large request body content out of inline configuration and into external storage (e.g., Azure Blob Storage or Azure Key Vault) and retrieve it via a separate lookup or variable before the Web activity.
3Step 3: Break complex Web activity configurations into smaller, sequential activities where possible to reduce per-activity payload.
4Step 4: Minimize the use of large dynamic content expressions in the request body; pass only essential parameters rather than full dataset outputs.
5Step 5: Re-run the pipeline and verify all activity payload sizes are within the supported limits.

Frequently asked questions

How is error 2002 different from error 2001?

Error 2001 relates to the execution output response being too large (over ~4 MB returned from the endpoint). Error 2002 relates to the activity's own payload — including its configurations and inputs — being too large to dispatch in the first place.

Can I store large request bodies externally and reference them in the Web activity?

Yes. A recommended pattern is to store large JSON payloads in Azure Blob Storage, retrieve the content using a Lookup activity, and then pass a trimmed or referenced version into the Web activity body to keep the configuration payload within limits.