HTTP action is failing with Cannot write more bytes to the buffer than the configured maximum

(0) Share

Report

Posted on by PaulineShare

HTTP action is failing with BadRequest. Http request failed as there is an error: 'Cannot write more bytes to the buffer than the configured maximum buffer size: 104857600.'

This is the HTTP action

URL: https://xxx.co.uk/main/ifsapplications/projection/v1/DocumentRevisionHandling.svc/DocIssueSet?$select=DocClass,DocNo&$filter=(DocClass eq '1001') and IsLatestRev eq 1&$top=1

{
  "Authorization": "*sanitized*"
}
{
  "Accept": "application/json"
}
 
If I use Postman I get a single line response as I would expect 

			@odata.etag
			W/"Vy8iQUFBU2E5QUFtQUFEcFVuQUFGOjIwMjQxMTExMTYxNDI4Ig=="
		
			@odata.id
			https://xxx.co.uk/main/ifsapplications/projection/v1/DocumentRevisionHandling.svc/DocIssueSet(DocClass='1001',DocNo='1002606',DocSheet='1',DocRev='REV04')
		
			DocClass
			1001
		
			DocNo
			1002606
		
			DocSheet
			1
		
			DocRev
			REV04

@odata.etag	W/"Vy8iQUFBU2E5QUFtQUFEcFVuQUFGOjIwMjQxMTExMTYxNDI4Ig=="
@odata.id	https://xxx.co.uk/main/ifsapplications/projection/v1/DocumentRevisionHandling.svc/DocIssueSet(DocClass='1001',DocNo='1002606',DocSheet='1',DocRev='REV04')
DocClass	1001
DocNo	1002606
DocSheet	1
DocRev	REV04

Categories:

Building flows

I have the same question (0)

All responses (4)

Answers (0)

Sort by

CFernandes 8,504 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Hey @PaulineShare You might have just a Limitation - https://learn.microsoft.com/en-us/power-automate/limits-and-config#message-size

To work around this limit, consider allowing chunking under the action content transfer settings. However, some connectors and APIs might not support chunking or even the default limit.
Note: When you send files through a connector, the overall size of the payload and not just the file needs to be under 100 MB.

If it helped you, please click "Does this answer your question?" and give it a like or mark it as Solution, it helps others in the community find answers more easily!
Connect With Me:
💼 LinkedIn: Clavin Fernandes
📺 YouTube: Clavin Fernandes
📝 Blog: clavinfernandes.wordpress.com
🌐 Community Website: PPUG.org
👥 Join our Community: Power Platform User Group

Was this reply helpful? Yes No
Suggested answer

Assisted by AI

PaulineShare 25 on at

Like (0)

Report
Copy link

Link copied!

Unfortunately, I have since learnt since posting that Power Automate is buffering the full response before applying the filter and top. The problem is an IFS OData v2 design issue with how IFS materialises entity sets server side so I cannot use Power Automate for this solution. I will need to look elsewhere

Was this reply helpful? Yes No
CFernandes 8,504 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Thank you. We handle files larger than 100 MB by processing them remotely and writing the output back directly to SharePoint using application (app-only) permissions. This approach avoids file size and timeout limitations while ensuring secure, reliable, and scalable processing without relying on user context.

If it helped you, please click "Does this answer your question?" and give it a like or mark it as Solution, it helps others in the community find answers more easily!
Connect With Me:
💼 LinkedIn: Clavin Fernandes
📺 YouTube: Clavin Fernandes
📝 Blog: clavinfernandes.wordpress.com
🌐 Community Website: PPUG.org
👥 Join our Community: Power Platform User Group

Was this reply helpful? Yes No
PaulineShare 25 on at

Like (0)

Report
Copy link

Link copied!

I am not trying to retrieve the file - only its metadata but the select (select=DocClass,DocNo) is being ignored when initially retrieving the data. The size of the file is not relevant for this scenario

Was this reply helpful? Yes No