So I'm having a lot of issues with reaching SharePoint throttle limits. I don't claim to understand this fully, but according to Microsoft the SharePoint connector can deal with 600 API calls within 60 seconds per connector.
Can somebody clarify what constitutes an API call? E.g. is a datasource refresh an API Call, then a new item, update item etc all seperate API calls?
What I'm doing isn't that complicated. I avoid delegation warnings and an example of what seems to cause some throttle issues would be soemthing like this...
That's a refresh > Update Records > Refresh.
If that was updating 50 records for example, how many API calls does that result in? And why might I be reaching throttle limits? It's worth noting that the list has 3,500 items currently but with indexed columns. I do expect this to grow quickly.
I have around 20 lists connected to my App. Never more than a handful of people working on the App at any one moment. So why might I be having these problems?
Any help appreciated.
Hi @DM2018 ,
Could you please share a bit more about your error message?
Based on the issue that you mentioned, I have made a test on my side, and don't have the issue that you mentioned. Actually, any operation related to SP List would be a Request API call. According to the formula you provided, the UpdateIf function would search through your whole SP List, then find these records match the filter condition, rather than just send requests to your filtered records.
In addition, each Refresh() function would also send a request call to your SP List server.
On your side, please consider modify your formula as below:
Filter(Productivity, Project_x0020_No=ProductivityActivityVariable.Project_x0020_No, Activity_x0020_Category=ProductivityActivityVariable.Activity_x0020_Category, Package=ProductivityActivityVariable.Package, Activity=ProductivityActivityVariable.Activity),
LookUp(Productivity, ID = ID1),
); /* <-- Is it not necessary to add another Refresh() function after this formula. */
Please take a try with above solution, then check if the issue is solved.
In addition, please make sure the Network on your side is in a good condition. The Network state would also affect the API Request Call speed.
Dear Kris Dai,
I am having some issues with Sharepoint Error :
Bad Request - not a valid connector (randomly appear about 1/10 times per day when using)
Etag MisMatch (when modifying an item which the user have just Submitted to Sharepoint List)
Just to understand the Limit of PowerApps/ Sharepoint better,
IF I have an app which 1000 people at the very same time to hit button Patch to Sharepoint List to create a new record of their Location and saved to Sharepoint Lists -> Will there be any trouble with Throttling?
I've been throttled from OneDrive, SharePoint, and Microsoft Flow (automate). I shut all my stuff down that pulled data using API calls, and it has been over a month and my account has not been released from the throttling. I get the throttling/too many requests message 95% of the time. It is ridiculous to advertise these tools for everyday users with no development experience, then engage permanent throttling on the accounts across the entire O365 system.
Fill out a quick form to claim your user group badge now!
Find out where you can attend!
Features releasing from October 2019 through March 2020
The largest Power BI, Power Platform, and Data conference in New Zealand