is there an intelligent way to cancel multiple flow runs at once?
I have a flow that reads from SharePoint list. This sometimes fails and sometimes just takes very long.
This flow is triggered by the HTTP call from another flow.
HTTP call performs several retries and the default number of 4 retries is just not enough.
I've increased the number of retries to 50 and this made things go crazy, with thousands of runs.
Apparently this brought the whole business to a halt and I now observe runs where a "scope" that contains 3 "compose" actions, each one run in under a second, - takes 25 min to complete.
So three questions:
1. how to cancel hundreds of runs at once
2. how to control for this kind of runaways
3. what to do about SharePoint response rate (read from the list of about 40 text entries)
In your first flow, the one that invokes HTTP action, are you expecting a response from the second one, right? This could explain the retry policy applying
Can you share a screenshot of your flow designs? Probably by introducing some changes we can avoid this problem in the future
P.D. I'm afraid I do not know any procedure to cancel more than one flow execution at once, let's hope someone can point us to the right direction.
Can you post a screen shot of your Flow - that would be a help for those trying to assist.
This is a settings of the calling HTTP action
This is the flow that gets stuck because this SharePoint list read sometimes returns Bad Request and sometime lasts more than an hour.
And here is "Scope" section with just 3 "Compose" actions, normally taking less than a second.
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