Azure / Azure/azure-functions-dotnet-worker

Blobtrigger continous triggering on blobs broken in 6.8.2 of Microsoft.Azure.Functions.Worker.Extensions.Storage.Blobs

Open
#3,499 1 comment 1 reaction 0 assignees View on GitHub
Needs: Triage (Functions) potential-bug
Dominant language
C#
Stars
466
Forks
215
Avg merge
3d 10h
Merged PRs (30d)
7

Description

### Description

We have quite a few applications running with the following stack:
.NET10
Azure functions v4
Isolated worker
Linux container

Now when upgrading to 6.8.2 of Microsoft.Azure.Functions.Worker.Extensions.Storage.Blobs, the blobtrigger stops working. It only works on startup/restart and sweeps the exisitng blobs, but the continous triggering on new blobs is broken.

We have downgraded to 6.8.1 and will do that for all our applications that use the BlobTrigger

### Steps to reproduce

Deploy and start application with a blobtrigger and the stack mentioned in description and version 6.8.2 of the package. Create a blob on a container the blobtrigger monitors and see if gets processed or not

Contributor guide

No contributing guide indexed for this repository

Research direction

Reproduce the BlobTrigger behavior using Azure Functions v4, the isolated worker, Linux, and Microsoft.Azure.Functions.Worker.Extensions.Storage.Blobs 6.8.2, then compare it with 6.8.1. Verify that existing blobs are swept on startup but newly created blobs are continuously processed; the issue is done when new blobs trigger processing reliably on 6.8.2.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, csharp, linux
Domain
backend, cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.