'Blob Batch' API-operation returns generic 'One of the request inputs is not valid' error

[ambarish2809]

We are trying to perform Blob Batch operation for delete operation using REST API. We receive a '202 Accepted' as the main response for the POST request, but a '400 One of the request inputs is not valid' as the batch response for the Delete sub-requests.

Note: We are able to perform the Blob Batch operation using the .NET SDK following the document https://docs.microsoft.com/en-us/dotnet/api/overview/azure/storage.blobs.batch-readme#examples. But, we want to perform the same using the REST API.

We tried reproducing the issue from the POSTMAN using different authentication methods (SAS, Shared Key, Bearer Token), however, we faced the same error for all the authentication methods.

Using Bearer token

For better isolation of the issue, we tried with a single batch request, but, no luck.

Please find the below screenshot for more information on the response headers and body.

Observations:

• The POST request returned a message as 202 Accepted whereas the Delete sub-requests returned '400 One of the request inputs is not valid' and the blob is not getting deleted from the storage account. • We have even analyzed the server logs for the operation. But, we could only see the POST request getting succeeded with HTTP 202. There are no logs getting logged for the Blob Batch delete operation failing with HTTP 400.

Note: We have followed all the pre-requisites as per the document of https://docs.microsoft.com/en-us/rest/api/storageservices/blob-batch.

Please let us know if we have missed anything here that is causing the issue.

Appreciate your kind help in this case!

[ghost]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @xgithubtriage.

Issue Details

---

We are trying to perform Blob Batch operation for delete operation using REST API. We receive a '202 Accepted' as the main response for the POST request, but a '400 One of the request inputs is not valid' as the batch response for the Delete sub-requests. **Note**: We are able to perform the Blob Batch operation using the .NET SDK following the document https://docs.microsoft.com/en-us/dotnet/api/overview/azure/storage.blobs.batch-readme#examples. But, we want to perform the same using the REST API. We tried reproducing the issue from the POSTMAN using different authentication methods (SAS, Shared Key, Bearer Token), however, we faced the same error for all the authentication methods. **Using Bearer token** For better isolation of the issue, we tried with a single batch request, but, no luck. Please find the below screenshot for more information on the response headers and body.  **Observations**: • The POST request returned a message as 202 Accepted whereas the Delete sub-requests returned '**400 One of the request inputs is not valid**' and the blob is not getting deleted from the storage account. • We have even analyzed the server logs for the operation. But, we could only see the POST request getting succeeded with HTTP 202. There are no logs getting logged for the Blob Batch delete operation failing with HTTP 400. **Note**: We have followed all the pre-requisites as per the document of https://docs.microsoft.com/en-us/rest/api/storageservices/blob-batch. Please let us know if we have missed anything here that is causing the issue. Appreciate your kind help in this case!

Author:	ambarish2809
Assignees:	akning-ms
Labels:	`Service Attention`, `Storage`, `needs-triage`, `question`
Milestone:	-

[dwsteele]

Was there any resolution on this? I am encountering the same issue with the REST API.

I get 202 Accepted and then:

--batchresponse_ea4d218e-4554-4ba3-abaa-05bd001d434c
Content-Type: application/http

HTTP/1.1 400 One of the request inputs is not valid.
x-ms-error-code: InvalidInput
x-ms-request-id: c6c556ba-701e-00bc-38c2-8b7b50000000
x-ms-version: 2022-11-02
Content-Length: 221
Content-Type: application/xml
Server: Windows-Azure-Blob/1.0

<?xml version="1.0" encoding="utf-8"?>
<Error><Code>InvalidInput</Code><Message>One of the request inputs is not valid.
RequestId:c6c556ba-701e-00bc-38c2-8b7b50000000
Time:2024-04-11T03:41:13.6598674Z</Message></Error>
--batchresponse_ea4d218e-4554-4ba3-abaa-05bd001d434c--

If it is accepted, shouldn't the error be scoped to a particular content-id?

Request headers:

POST /container?comp=batch&restype=container&se=2028-04-11T10%3A20%3A38Z&sig=XXX&sp=rwdlacupiytfx&spr=https&srt=co&ss=bfqt&st=2024-04-10T02%3A20%3A38Z&sv=2022-11-02 HTTP/1.1
content-length:813
content-md5:C4F1j9GQM1/Y97U2H9bGhw==
content-type:multipart/mixed; boundary=XyKQzd3-Y5abPhU_UcxJd8f_70xtP3j-IYtmxNL
host:container.blob.core.windows.net

Request body:

--XyKQzd3-Y5abPhU_UcxJd8f_70xtP3j-IYtmxNL
content-type:application/http
content-transfer-encoding:binary
content-id:0

DELETE /container/demo-repo/backup/demo/20240410-012206F/bundle/1?se=2028-04-11T10%3A20%3A38Z&sig=XXX&sp=rwdlacupiytfx&spr=https&srt=co&ss=bfqt&st=2024-04-10T02%3A20%3A38Z&sv=2022-11-02 HTTP/1.1
content-length:0

--XyKQzd3-Y5abPhU_UcxJd8f_70xtP3j-IYtmxNL
content-type:application/http
content-transfer-encoding:binary
content-id:1

DELETE /container/demo-repo/backup/demo/20240410-012206F/bundle/2?se=2028-04-11T10%3A20%3A38Z&sig=XXX&sp=rwdlacupiytfx&spr=https&srt=co&ss=bfqt&st=2024-04-10T02%3A20%3A38Z&sv=2022-11-02 HTTP/1.1
content-length:0

--XyKQzd3-Y5abPhU_UcxJd8f_70xtP3j-IYtmxNL--

[estruyf]

I am experiencing the same as @dwsteele with a similar API request to the batch API.

[dwsteele]

Is anybody monitoring these issues?