How to optimize Azure Logic App to reduce unnecessary runs?

Question

The current implementation of an Azure Logic App (Standard) uses a Recurrence trigger, leading to processing every item regardless of whether they meet the specified condition. This results in unnecessary executions and increased overall costs.

What strategies or best practices are recommended to structure the Logic App, or are there alternative triggers or filtering mechanisms that can be used to ensure it only runs when the required condition is met? Any suggestions or guidance would be highly appreciated.

Answer 1

Hi @Jacek Leo ,

I do agree with @Richard Parker, when you set the recurrence trigger, it triggers and runs the logic app whenever the condition of time is met.

For different services, Logic apps has multiple triggers. For blobs you have blob trigger in blob, It checks the modification, created and others. In the same way, it has for sql triggers or http trigger. Http trigger(When a http request is received) is a manual trigger when ever you call the logic app, it triggers

If you are looking for a specific event to happen, you can use Event grid trigger.

You can also use Event hubs, whenever event occurs in Event hub it triggers:

Hope this helps.

If the answer is helpful, please click Accept Answer and kindly upvote it. If you have any further questions about this answer, please click Comment.