Have you ever noticed on your Automated flow with trigger for e.g Item created or modified on a SharePoint list will not run immediately as & when there was an item either created or modified in the list? The reason is all the automated triggers has a recurrent frequency schedule which is set to 3 mins, it means it looks for the changes in the SharePoint list every 3 mins. To check this, go to Peek Code on the trigger to check the interval frequency
For the When an Item is created trigger
This setting cannot be changed in Power Automate but with Azure Logic Apps you can adjust this setting. For more details on the pricing, refer to this link
If there is further delay in the trigger to get fired, check your flow plan since it has a dependency. As per information gathered from the Flow community forum
The maximum flow frequency for User based or App based plans is 1 minute, however if you are using Free plan it will be 15 minutes. And if it is Flow for Office 365 (Plan from your Enterprise license E3, E5 etc) and Flow for Dynamics 365 it will be 5 minutes.
From the FAQ page in the Microsoft site for Flow, it says
Your plan determines how often your flows run. For example, your flows may run every 15 minutes if you’re on the free plan. If a flow is triggered less than 15 minutes after its last run, it’s queued until 15 minutes have elapsed.
The same trigger with Logic apps which has options to update the recurrent frequency interval
If you are new to Logic Apps, follow this article from Microsoft to get started. The other advantage with Logic apps is there is a code view to update & Save which is not the case with Power Automate. In Power Automate, you can only view the code & not update
Hope this information was useful in some way. If you have any comments, let me know on the comments section.
One thought on “Automated trigger recurrence frequency – Power Automate”
Does this also mean that triggers activated less than 15 min since the last will cause previous ones to run again an Issue that I seem to be having?