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.
TYPEERROR FAILED TO FETCH SOFTWARE
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)
