1

I want to implement a logic app workflow which is using a trigger:

Logic App: Standard Connector: Azure File Storage Trigger: When a file is added or updated

Configuration: giniusdata/Plot/PDF/PDFOUT-Test/NFP/{name} Configuration of the trigger: giniusdata/Plot/PDF/PDFOUT-Test/NFP/{name}

If I now upload a file to "giniusdata/Plot/PDF/PDFOUT-Test/NFP/", the trigger is working as expected, but if I upload a file to "giniusdata/Plot/PDF/PDFOUT-Test/NFP/Circuits/" or any other subfolder (or even sub-sub-folder), the trigger won't fire.

Is there a possibility to reconfigure the trigger, that it's firing on subfolders as well?

1 Answer 1

0

The standard connector for Logic Apps does not monitor sub-folders. This is a known limitation of the connector, which means that you're going to need to use a work-around to achieve the behavior you're looking for.

The way I would go about it, would be to setup a request trigger in your Logic App instead, and have the Storage Account perform the request when changes are detected.

To setup your Storage Account to call your Logic App request trigger, simply navigate to your Storage Account in Azure portal and use the Events menu option. Here, you'll be able to create a new Event Subscription using the Blob Created event type.

For your endpoint, simply select Web Hook and use the endpoint from your new Logic App request trigger.

You can add filters for specific containers by using Subject Filters in your new Event Subscription.

Sign up to request clarification or add additional context in comments.

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.