BlobTrigger is jammed

[davidmatson]

BlobTrigger keeps firing even after it's been processed. Today, we don't have any way to avoid continuous automatic firing in every scenario. For example, consider:

public static void ProcessBlobIntoQueue([BlobTrigger("container/{name}")] string blob, [Queue("myqueue")] out string queue)
{
}

or:

public static void ProcessBlobIntoBlob1([BlobTrigger("container/{name}")] string blob, [Blob("container/out") CloudBlockBlob output)
{
 // output may or may not be created depending on the code inside this function.
}

public static void ProcessBlobIntoBlob2([BlobTrigger("container/{name}")] string blob, [Blob("container/out", FileAccess.Write) Stream output)
{
 // output may or may not be created depending on the code inside this function.
 // if it doesn't write to output; it won't be created.
}

We could make the first an indexing error, but what about the second? I doubt we can make the third an indexing error.

If BlobTrigger ever keeps firing, that's quite surprising to the user, as well as potentially quite expensive.