Azure blob triggered function only triggering on some blobs

Question

I have two blob triggers which I want to trigger on. One works and one does not!

I use Azure Storage Explorer to make sure blobs are uploaded to each blob, scanFiles will never trigger, and scanExports seem to always trigger.

Question: What can cause some blobs to not trigger an Azure function?

    [FunctionName("scanFiles")]
    public static async Task FilesScan([BlobTrigger("files/{newBlobName}", Connection = "BlobConnectionstring")]CloudBlockBlob newBlob, string newBlobName, ILogger log, ExecutionContext context)
    {
        await VirusScan(newBlob, newBlobName, log, context);
    }


    [FunctionName("scanExports")]
    public static async Task ExportsScan([BlobTrigger("exports/{newBlobName}", Connection = "BlobConnectionstring")]CloudBlockBlob newBlob, string newBlobName, ILogger log, ExecutionContext context)
    {
        await VirusScan(newBlob, newBlobName, log, context);
    }

They are not deployed currently. This happens during offline development in visual studio. They are defined in the same file, calling the same private function, so they are as identical as possible — Jeppe
Have you tried (As per Microsoft's recommendation) to put each Function into its own class and folder? — Alex
I have not, I'll try this tomorrow. I haven't taken notice of this suggestion before, where did you find it? — Jeppe
See: docs.microsoft.com/en-us/azure/azure-functions/… . An excerpt: "Each subfolder contains the code for a separate function" — Alex

Jeppe Jeppe · Accepted Answer · 2019-09-23T10:19:01

I found that the issue was because one of the blobs were considered High scale, which triggers this bug and also makes the host process kill itself when run locally (see this issue)

Azure blob triggered function only triggering on some blobs

1 Answers