Photo by Mohammad Rahmani on Unsplash

System.InvalidOperationException: Expected an HTTP status line, not changesetresponse with Azure.Data.Tables

Thomas Pentenrieder
medialesson
Published in
Jan 31, 2022

--

If you are getting this error message, it’s probably because you tried to process more than 100 TableTransactionActions with a single SubmitTransaction call against the Azurite Storage Emulator.

Unfortunately this is not well documented with the new Azure.Data.Tables SDK, but since this is a hard limit on the Azure Table Storage side of things here the same rules apply as with the old Microsoft.Azure.Cosmos.Table package:

A batch operation may contain up to 100 individual table operations, with the requirement that each operation entity must have same partition key. A batch with a retrieve operation cannot contain any other operations. Note that the total payload of a batch operation is limited to 4MB.

Caution: You can batch entities across PartitionKeys when working against Azurite, but this will fail with a real Azure Table Storage in the cloud!

--

--