ERR_FR_MAX_BODY_LENGTH_EXCEEDED when passing 5MB file

[mihaiLucian]

Describe the bug
I want to build a durable function in typescript. This function will take a big json file(it can go between 0-20 MB) and then do some processing with the data from the JSON file.

I use postman to provide a form-data with my file and start the orchestrator.
Below exception is thrown:
Exception: Error [ERR_FR_MAX_BODY_LENGTH_EXCEEDED]: Request body larger than maxBodyLength limit
Stack: Error [ERR_FR_MAX_BODY_LENGTH_EXCEEDED]: Request body larger than maxBodyLength limit

Investigative information

• Durable Functions extension version: [2.*, 3.0.0)
• durable-functions npm module version: 1.5.4
• Language (JavaScript/TypeScript) and version: 4.0.0
• Node.js version:14.19.1

If deployed to Azure App Service

• Timeframe issue observed:
• Function App name:
• Function name(s):
• Region:
• Orchestration instance ID(s):

If you don't want to share your Function App name or Functions names on GitHub, please be sure to provide your Invocation ID, Timestamp, and Region - we can use this to look up your Function App/Function. Provide an invocation id per Function. See the Functions Host wiki for more details.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

While not required, providing your orchestrator's source code in anonymized form is often very helpful when investigating unexpected orchestrator behavior.

Expected behavior
A clear and concise description of what you expected to happen.

Actual behavior
A clear and concise description of what actually happened.

Screenshots
If applicable, add screenshots to help explain your problem.

Known workarounds
Provide a description of any known workarounds you used.

Additional context

• Development environment (ex. Visual Studio)
• Links to source
• Additional bindings used
• Function invocation IDs

[codeHysteria28]

Hey. And what are you actually doing with the file ? Saving to Azure Storage ? If so, then you will need to break the file into chunks.Assume that you try to write more than 4 megabytes (MB) of data to a file on Azure Storage, or you try to upload a file that's larger than 4 MB by using the SAS url (REST API) or HTTPS PUT method.

Could you maybe describe the whole scenario, please ? Thank you

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

[davidmrdavid]

Removed label so this issue won't auto-close. This is a legitimate report, just low-priority given that large inputs are not "best practice" in DF

[ankuratudemy]

We are facing the same issue. It's sort of related to #93

Our use case is to trigger durable function with "type": "blobTrigger",

We have excel uploads with thousands of rows. Can we have maxBodyLength: Infinity,. set along with

maxContentLength: Infinity, in this

1dbfb28

[ankuratudemy]

Removed label so this issue won't auto-close. This is a legitimate report, just low-priority given that large inputs are not "best practice" in DF

Hi, Is there a workaround possible ? Any suggestions on how we can pass for example big JOSN files to be process by activity in loop ?

[davidmrdavid]

Hi @ankuratudemy: if you have this data in blob storage, you could just pass in a data identifier to your activities, and load the data in the activities themselves.

What matters it to ensure that large objects are not returned from activities, and also not used inside DF APIs (such as callActivity) within orchestrators.