Logic App stops detecting Blob Storage changes

Josh Rogers 21 Reputation points
2020-07-21T15:26:12.4+00:00

We have a Logic App that monitors a blob storage path. On Sunday evening that blob storage location reached approximately 33k blob files. At this point, our logic app continued to trigger, once every minute, but each trigger was skipped as if it couldn't find any new files. After trying different things we began moving blobs out of the blob path. As soon as we did this the logic app began to detect all the missing files it had "skipped" since Sunday and process them. So, there seems to be some arbitrary limit that we can't seem to find documented anywhere where Logic Apps begin to fail to find new blob files.

We would really prefer not to have to move these files out of this location just so we can ensure the logic app continues to work. So, is there some arbitrary limit and if so what is it specifically, and what is the proposed best practice/workaround?

Azure Blob Storage
Azure Blob Storage
An Azure service that stores unstructured data in the cloud as blobs.
2,920 questions
Azure Logic Apps
Azure Logic Apps
An Azure service that automates the access and use of data across clouds without writing code.
3,203 questions
0 comments
Accepted answer
  1. Pramod Valavala 20,636 Reputation points Microsoft Employee
    2020-07-22T07:19:03.99+00:00

    There is a Maximum trackable number of items inside of a virtual folder for trigger limit of 30k mention in the connector reference doc which I believe is what you are hitting.

    The alternative is to leverage Event Grid and its corresponding trigger for Logic Apps, which gives you the added advantage of not having to poll the blob container and near instance trigger of the Logic App when a blob is added.

    0 comments

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.