[BUG] [Storage] WebJobs Extension not reading MaxDequeueCount

[amnguye]

Library name and version

Microsoft.Azure.WebJobs.Extensions.Storage.Blobs; Microsoft.Azure.WebJobs.Extensions.Storage.Queues

Describe the bug

See this document for reference.

https://learn.microsoft.com/en-us/azure/azure-functions/functions-bindings-storage-blob-trigger?tabs=in-process%2Cextensionv5&pivots=programming-language-csharp#concurrency-and-memory-usage

In the v4 WebJobs Storage Extension it used the property maxDequeueCount in the host.json but looks like in the current version (v5) it's not reading the value at all and not applying it to the QueueOptions.

To clarify this affects the blob trigger function when added.

Expected behavior

The maxDequeueCount is respected host.json and applied to the QueueOptions.

Actual behavior

It's being ignored if applied.

Reproduction Steps

In the host.json file add something like

{
  "version": "2.0",
  "extensions": {
    "queues": {
      "maxDequeueCount": 1
    }
  }
}

QueueOptions should look something like

{
  "BatchSize": 16,
  "NewBatchThreshold": 16,
  "MaxPollingInterval": "00:01:00",
  "MaxDequeueCount": 5,
  "VisibilityTimeout": "00:00:00",
  "MessageEncoding": "Base64"
}

Environment

n/a

[amnguye]

Looks like we misunderstood the issue, this is something that just isn't carried forward by design in v5.

https://learn.microsoft.com/en-us/azure/azure-functions/functions-bindings-storage-blob-trigger?tabs=in-process%2Cextensionv5&pivots=programming-language-csharp#concurrency-and-memory-usage