Share
Report
81Hi,
In the Flow I am currently building there is the potential for me to run into a number of limits, in particular the API Call limit.
Now, for the predefined Connectors that I use (oneDrive for Business, Excel Online for Business, JIRA) the API Call limit is set to 100 / minute. Given that, it is unlikely for my flow to exceed those numbers (but it may happen nonetheless). Also, the looping depth limits for the 'for each' action are more than sufficient.
Where I am a bit concerned is how this works with Custom Connectors. I have not been able to find any information on if there are any API Call limits imposed on Custom Connectors (I am running two, one for JIRA, the other for the MS graph API) and how Custom Connectors act within 'for each' loops.
Thus my questions are as follows:
- Are Custom Connectors subject to any API Call Limits, and if so, where are they defined?
- Do Custom Connectors impact the looping depth limits, and if so, how?
- In case I do run into any API Call Limits with any of the Connectors (predefined or custom), what is going to happen?
- Is there a recommended way for me to build in some sort of defense against reaching the API Call Limits (enforce waits, timeouts, ...)?
With regards to question 3., I have tried testing this with a predefined Connector a while back (MS Planner Connector, I think). The result has been a 5 minute time-out & resume, with multiple time-outs and resumes possible within a single flow run. I assume that this is standard behaviour for all Connectors (or at least for all predefined ones), but I am interested if anyone can confirm this.
Thanks in advance, cheers,
JP
All responses (
Answers (
