Starting yesterday, I'm finding that I am getting the 'Rate Limit is Exceeded' message repeatedly on an existing app that previously rarely, if ever, got this error.
My understanding was that the Rate Limit applied to transactions rather than records, e.g. a single delegable filter command would be one transaction irrespective of the number of records returned. Is this correct? Is there a resource which defines what actions count agains the Rate Limit?
I have reduce the frequency with which I refresh data sources and that has definitely helped, reduce, but not completely eliminate the 'Rate-Limit' warnings.
To help trouble-shoot, is there any way of viewing the transaction Rate while testing an App to try to determine if the limit is being approached and how much each command is eating up the limit?
I have tested again today and I'm not getting the Rate-Limit warning so far. I'll try putting some of the original refresh statements back in to see if that triggers it again.
I'm suddenly getting this error as well. The app is in development, so the only person using it is me. Any insights regarding what this is trying to tell me or how to avoid it?
My understanding is the issue is caused by making too many 'calls' to SharePoint within a given time frame. I've most commonly seen this with galleries that have multiple LookUps (common when trying to work with a 'normalised' data set with a parent and one or more child lists in SP). For each row in the gallery, the LookUp fires individually, so if the Gallery returns 100 rows and each row has two LookUps, you're making another 200 requests to SharePoint.
Previously the solution would have been to use SQL instead of SharePoint for more 'sophisticated' data structures and handle the lookups server side with a view. Unfortunately the new licensing puts this solution beyond many people's budgets. Instead, try to re-design your App to make fewer calls to SP per minute.
Hmmmm... I am entering a total of 11 items into a collection, with a Patch function. A repeating table, per a tutorial from @Shanescows . And yes, it is entering a total of 3 items per each to a sharepoint list. I am getting the same error, after several minutes of 'the ants marching across the top of the screen'. Any ideas of a way around this, or is this just a shortcoming of Sharepoint?
Featuring samples like Return to the Workplace and Emergency Response Applications
We're excited to announce our first cross-community 'Can You Solve These?' challenge!
Reopen responsibly, monitor intelligently, and protect continuously with solutions for a safer work environment.
We are excited for the next Super User season.
FIll out a quick form to claim your community user group member badge today!
Features releasing from October 2020 through March 2021