CloudQueue.DeleteMessageAsync(CloudQueueMessage) for message that became visible

Scenario 1

1. msg1 (CloudQueueMessage) is received with visibility timeout set to 30 seconds.
2. processing is taking much longer than 30 seconds
   1. while processing of msg1 is happening, msg1 becomes visible on the queue
   2. another competing consumer received the message as msg2
3. msg1 is attempted to be deleted using CloudQueue.DeleteMessageAsync(msg1). 💥

Exception is thrown The remote server returned an error: (404) Not Found.

Scenario 2

1. msg1 (CloudQueueMessage) is received with visibility timeout set to 30 seconds.
2. processing takes 40 seconds
3. msg1 is kept around and later deleted using CloudQueue.DeleteMessageAsync(msg1).

Message is deleted.

The question

Should the second scenario throw an exception? In the world of the competing consumers it sounds wrong that one can delete a message with an expired PopReceipt.

Side note: This is also very inconsistent with ASB, where once message lock is expired, no operations can happen on the message.

[SeanFeldman]

Raised UserVoice issue here

Please vote there as @mirobers has indicated. This is a storage queue server-side service issue.

[mirobers]

Please do use the feedback link above to register this request so others can vote on it as well. I’m closing the issue here as it doesn’t relate to the client; we can track the request in the feedback forum instead. Thanks for your input!