My flow is now taking 15 minutes to 1 hour to complete, whereas previously it would only take a few seconds. It's caused a bit of chaos, as a seperate flow, which is dependant on the result of this flow, is being triggered by users prior to this flows completion.
Our business is currenly operating on a free flow plan, and my *guess* is that my flows have been throttled, but I don't see a clear way to access information about flows and whether or not throttling is occuring.
Has anyone else experienced something like this, and was throttling to root cause? And if so, how does one access information concerning flow runs and limits? Is there a 'You have x amount of flow runs left this month' screen?
Hi @cfebvre ,
Could you please share a screenshot of the configuration of your flow?
My flows always works well and don't have the issue that you mentioned.
There is no any way in microsoft flow could let user access information concerning flow runs and limits, the screen'You have x amount of flow runs left this month' that you mentioned is not supported in microsoft flow currently.
Community Support Team _ Alice Zhang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi @v-alzhan-msft Alice,
Thanks for getting back to me. I've attached both the configuration of the flow, an example run, and the add image controls in powerapps.
Basically, the purpose of the Flow is to allow users to attach any jpeg to a list item within powerapps, but have it immediately renamed Image001.jpg - Image010.jpg (a user can attach up to 10 images for a given list item within my powerapp).
The avoids the problem of Sharepoint automatically reordering attachments alphabetically, and allows another flow to pick up a correctly labelled image for different purposes.
When a user uploads 10 images (each one with a distinct 'Add Image' control within the powerapp, the flow will trigger 10 times.
The first image trigger always succeeds in its flow run. Subsequent runs for the same List item (Image002.jpg, Image003.jpg) always 'fail', however - the flow always 'succeeds' in creating the image and naming it correctly.
Over the last couple of months, the Flow has performed correctly (even though it says it fails), and images have been attached to the list item within one minute (usually it only takes a few seconds), but this past week the flow has slowed down to a crawl, especially when up to 10 images are uploaded by the user.
So the root question is what is causing this to occur?
- Is the fact that the flow 'fails' causing a delay?
- Or have I hit a limit in flow runs, resulting in a delay to service?
- Or is there another reason why this might have suddenly occured?
Found this on https://docs.microsoft.com/en-us/flow/billing-questions
What happens if I try to execute runs too frequently?
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.
Check out the new Process Advisor community forum board!
Check out new user group experience and if you are a leader please create your group
On-demand access to all the great content presented by the product teams and community members! #MSBizAppsSummit #CommunityRocks
Check out how to claim yours today!