Forum Discussion
Issue with Logic Apps running MANY times after enabling it
I am facing same issue after enabling the logic app. I am using Logic app consumption and trigger is Recurrence set to once a day.
According to MS doc -
For the Recurrence trigger when you are setting the concurrency as one for every one hour it means that your workflow will be triggered every one hour. If the trigger misses recurrences, for example, due to disruptions or disabled workflows, the Recurrence trigger doesn't process the missed recurrences but restarts recurrences with the next scheduled interval.
Whereas when you use Sliding Window trigger it will trigger every one hour. If recurrences are missed for any reason, for example, due to disruptions or disabled workflows, this trigger processes those missed recurrences. Let's say if you have disabled the trigger for 5 hr then there will be five misses but as soon as you have enabled the trigger again the logic app starts 5 times simultaneously.
Because of this reason, I started with Recurrence trigger only and now this issue is different. It is hard to figure out the root cause though trigger is Recurrence.
Has anyone able to figure out the reason for this behaviour ? I have various batch jobs run using recurrence and after enabling any logic app it is showing same behavior.
I have re-deployed the ARM, I have deleted and created a new logic app but the issue still persists. Any help is appreciated.
You've made it a lot clearer to me on how that sliding window works. It actually sounds like a very good idea and I feel like I should be using this instead... although I've just removed all of them and replaced with a Recurrence trigger.
So my cure before was to delete the logic app and create a new one with a new resource name. I didn't have that issue after that.
Have you tried this?
Dan
