You'd do this using the CHILD FLOW action which will only appear if you have saved all your related flows inside the same solution (AND created them inside the solution as well and not outside and then imported them in, since this can bring problems as well). The advantage of doing this is you can then call all flows contained in your solution from one another. The way to do this without a Power Automate per user license would be to use the Solutions section of your Power Automate studio.Ī solution is basically a container that allows you to save different related flows into it. This approach has to be handled with caution since before starting you need to make sure to know how to handle data through JSON and also since if you (and your users) are all licensed up properly (in case you are thinking on using HTTP requests to move data between the different flows since that is a premium connector). This would mean build a squeleton flow which would then call different parts of your original flow. The second solution is to partition your original flow. That will mean that your actions will use different connections to make the call and will not get throttled. Once you've done that you can randomize the use of those between all the actions that are from the same service (ie excel). So you would have to go into the elypsis of one of your actions (of the problematic connector, in my case Excel ones) and from there create extra connections. There's 2 solutions to get out of this problem, the first one is to create more connections for the same service within the flow you are writing. Since AFTER doing that the problem persisted I thought on how many calls where my connections making to the microsoft APIs and if this could be the culprit and it effectively was. What you want is not to have a single connection per service used but many to distribute the calls and not get throttled. I had previously whitlisted all the domains and IP addresses listed here as it was indicated in microsoft documentation to rule out this being the problem. That's why I was getting the Failed to fetch error.
This means that microsoft is stopping me from continuing doing calls to them and getting all the info I need for my flow to load all the pertinent data and show it to me. This turned out to be true since when I opened my Flow in edit mode while monitoring the calls made to APIs I could see that some of them were returning the 429 error which corresponds to too many requests. I've run some tests with Fiddler which lets you monitor all http requests done (among other things) when opening web pages or software since I thought that maybe I the problem could be in too many calls being done by the connectors to the microsoft APIs and being throttled as a result.
I've been thinking of this problem at large since I had it too.
0 kommentar(er)
