[BUG] Storage Queues: Method QueueClient.ReceiveMessagesAsync does not retrieve invisible queued messages

[twentytwokhz]

Describe the bug
When calling the ReceiveMessagesAsync on a queue containing messages that have visibilityTimeout set, no data is retrieved and the response list is empty

Expected behavior
We should be able to see the list of queue messages (based on filter criteria in call)

Actual behavior (include Exception or Stack Trace)
No message is retrieved from the queue

To Reproduce
Steps to reproduce the behavior (include a code snippet, screenshot, or any additional information that might help us reproduce the issue)

1. await queueClient.SendMessageAsync(base64EncodedMessage, TimeSpan.FromSeconds(20));
2. var queueMessages = await queueClient.ReceiveMessagesAsync();
   => queueMessages.Value.Length is 0
3. queueMessages = await queueClient.ReceiveMessagesAsync(visibilityTimeout: TimeSpan.FromSeconds(20));
   => queueMessages.Value.Length is 0

Environment:

• Azure.Storage.Queues 12.1.1, 12.2.0 (these I tried)
• Running on .NET Core 2.2 web app
• Visual Studio 16.5.0 Preview 2.0

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

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

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

[seanmcc-msft]

Hi @twentytwokhz,

QueueClient.ReceiveMessagesAsync() calls the Get Message REST API.

If you scroll down to the remarks section, it says:

"When a message is retrieved from the queue, the response includes the message and a pop receipt value, which is required to delete the message. The message is not automatically deleted from the queue, but after it has been retrieved, it is not visible to other clients for the time interval specified by the visibilitytimeout parameter."

This means that if the visibility timeout has been set on a message in a previous ReceiveMessagesAsync() call, it will not appear in subsequent ReceiveMessagesAsync() calls until after the timeout has expired.

-Sean