When your Azure blob trigger based Workflow is not triggering

 

What could be more irritating when you see your Azure blog trigger isn't getting fired, even though files are getting dumped into your azure blob incessantly? What could be the reason?

Well, the answer is very simple:

Maximum trackable number of items inside of a virtual folder for trigger

= 30000

Which means, if your Azure blob doesn't have a purging facility associated with it, eventually the container will reach to such a threshhold, that your workflow will simply fail to detect any blob, when it gets added.

Solution:

a. Either you design your blob storage to be limited to around 1000-2000 files, then it will be really, really great.

b. Or else you could enable auto-archiving of your azure blob storages, with a certain frequency, as is documented in the following MS link:

https://learn.microsoft.com/en-us/azure/storage/blobs/archive-blob?tabs=azure-portal