What changed in delete message api v2?

Tlek Aipov (Akvelon INC) 1 Reputation point

Hello team.
A question about updating documentation and api for deleting messages from Azure Queue.
We use this api for a connector through which users can interact with Azure Queue.
One of the customers contacted us with the following problem: from about the beginning of July,
the customer began to receive errors when trying to delete messages from the queue.
Namely, that there is no message in the queue.
To delete messages, we use the following api: https://learn.microsoft.com/en-us/rest/api/storageservices/delete-message2.
As far as I noticed, the documentation was updated on July 9, 2022.
According to the new version of the documentation, messages cannot be deleted if their properties have changed - messageid or pop Receipt.
The customer has several GetMessage calls before deletion, and only after that the Delete Message call, but with the old Pop Receipt, which was received when the Get Message was first accessed. This is the cause of the errors.
The customer claims that with the old version of the api, deleting messages worked taking into account several GetMessage requests.
Can you please provide a description of the changes that have occurred in the new version of the api?
In order to understand why the old version worked. Perhaps there was no need to use the current Pop Receipt property?

Azure Queue Storage
Azure Queue Storage
An Azure service that provides messaging queues in the cloud.
98 questions
{count} votes

1 answer

Sort by: Most helpful
  1. SaiKishor-MSFT 17,206 Reputation points

    @Tlek Aipov (Akvelon INC) Thank you for reaching out to Microsoft Q&A. I understand that your client is having challenges with the Delete message API as it requires the pop receipt property in order to delete messages currently.

    I checked regarding this with the PM for this service and confirmed that with respect to Delete behavior, it has always been this way i.e., it had always required the most recent pop receipt and that things haven't changed recently. This feature is to make sure that the customer does not delete a message that they didn't pull. Hope this helps.

    Please let us know if you have any more questions and we will be glad to assist you further. Thank you!


    Please accept an answer if correct. Original posters help the community find answers faster by identifying the correct answer. Here is how.

    Want a reminder to come back and check responses? Here is how to subscribe to a notification.

    0 comments No comments