Cannot write more bytes to the buffer than the configured maximum buffer size: 104857600.

(1) Share

Report

Posted on by NS-10041416-0

184

Hi,

I am connecting to dataverse table to get values through power automate.

But I am encountering an issue 'Http request failed as there is an error: 'Cannot write more bytes to the buffer than the configured maximum buffer size: 104857600.'.'

Issue

So please let me know if I am making any mistake here

Regards,

Sudheer

Categories:

Building flows

I have the same question (0)

All responses (8)

Answers (1)

Suggested answer

Tomac 3,966 Moderator on at

Like (0)

Report

@NS-10041416-0 I'm assuming this table has a significant number of columns, yes?

You'll need to use Select Columns to only get the columns you want to work with, as well as maybe filter a bit more to cut down on the number of rows returned or use Row Count to limit the number of rows you get back.

The issue is the amount of data that's being returned by your query is too large for the Power Automate cache to store.

Was this reply helpful? Yes No
lbendlin 8,479 Super User 2025 Season 2 on at

Like (0)

Report

100 MB is a hard limit for message size, for some reason.

Limits of automated, scheduled, and instant flows - Power Automate | Microsoft Learn

Was this reply helpful? Yes No
NS-10041416-0 184 on at

Like (0)

Report

Hi @Tomac,

Thanks for the response.

Now I have specified the column in the List of Rows as below

But I am getting an error as

Regards,

Sudheer

Was this reply helpful? Yes No
lbendlin 8,479 Super User 2025 Season 2 on at

Like (1)

Report

Column titles should ideally not have spaces. You need to encode that via _x0020_

Was this reply helpful? Yes No
Suggested answer

Tomac 3,966 Moderator on at

Like (0)

Report
@NS-10041416-0

As @lbendlin said, you'll need to encode the space character in your column name if it does indeed have a space, like so:

Primary_x0020_Email

If this resolves your issue, please remember to mark the helpful comment(s) as the answer.

Was this reply helpful? Yes No
NS-10041416-0 184 on at

Like (0)

Report

Hi,

I have updated the same but no luck

Regards,

Sudheer

Was this reply helpful? Yes No
lbendlin 8,479 Super User 2025 Season 2 on at

Like (0)

Report

The actual field name may be different from the display name.

Was this reply helpful? Yes No
Verified answer

Michael E. Gernaey 53,493 Super User 2025 Season 2 on at

Like (1)

Report

H i@NS-10041416-0

You would not put the name with encoding as its dataverse. The display name does not mean anything (at all) as it relates to accessing it.

You need to go to the Table definition and grab the logical name, in all lower case.

So go to the Table, click Advanced, grab the logical name, which is all lower case and place that there.

The Label isn't what you ever use in dataverse, except in a Canvas app as it auto maps it to the proper logical name .

its most likely something like

prefix_primaryemail, where prefix is your solutions prefix.

P.S. There are also ways to increase the max bytes so its greater than what you see in your error. Not saying you should but you can.

Cheers

If these suggestions help resolve your issue, Please consider Marking the answer as such and also maybe a like.

Thank you!
Sincerely, Michael Gernaey

1 people found this reply helpful.

Was this reply helpful? Yes No