Length content error on Get Row - Excel Business

[DrStockton]

Hi all,

Since this morning (CET), I am getting tons of errors on Get Row action on Excel Business conector.

The error is 413: Length of response's content is '67307494' being the maximum value '52428800'.

It is the first time this error shows up and I have executed it over 5,000 times same action on the same flows (at least 8 different flows)

It seems like the the Key Value is processing as a "contains" instead of an "equal" (always worked in that way)

The Key Column is an ID column with IDs between 1 and 999999;

When it worked, it returned 17 fields (columns) with aprox 1,000 characters between all the fields

I have tried putting the IDs as a numbers, as a texts... but nothing.

Any guess? thanks in advance

[trad]

The Excel file is too big. The connector will only work with max 50 MB file size.

[DrStockton]

Thanks Trad! My excel is 25 MB file size

[trad]

Well in fact the connector info page https://docs.microsoft.com/en-us/connectors/excelonlinebusiness/ says the limit is 25 MB. The error message saying "52428800" corresponds to 50 MB though.

[DrStockton]

Thanks Trad, I really appreciate you help because I am lost 😞

I have reduced my file to 22MB because it was 25.847 KB but the problem is the same 😞

I backup the Status File every 2 business hours and you can find the file size I am having over the last days. The red line I included is when the last success flow I had 😞

Since last night (CET)... the error appears 

My history... 😞This is the errror after executing it with the new Status file with 22MBI have reduced the file to 22MB but with no success 😞Backup Status File each 2 business hours - Red line shows the last time my flow had success

[DrStockton · Accepted solution]

Now is solved

Hi all, specially to @trad who kindly helped me.

The issue has disappeared with no change on my side: The file is the same, with same size.

So it seems the change that MS made on the Excel Business Connector on Monday night (CET) regarding dates, probably broke something else and now is solved.

Now I can enjoy the weekend because it was a huge issue!