The "Rate Limit exceeded" error means that you hit the limit of API calls for the SQL Server connector.
There is a limit in the API calls for the SQL Server connector -- 800 calls per 10 seconds. More details about the API Calls limit for connectors in PowerApps/Flow, please check the following article:
In order to fix this issue, please consider take a try to reduce the API calls from your app to the SQL Server connector.
On your side, you should patch less records (e.g. 50 records) to your SQL table once time, and then patch the next 50 records, etc.
We are running into very similar issues. From what I can find SQL Server limit is 100 calls per 10 seconds. We want to roll out an app to a larger number of people. The app needs to have real time data for certain values.
Did you find anything that has helper you over come these throttling limitations of PowerApps?
This is where powerapps falls over and i feel definitely needs looking at for paying customers.
The only thing i have been able to do is where i was using concurrent to process updates to multiple tables at once (reducing time for the end user) i have had to process them individually which adds about 2 minutes to the upload for me.
Since there is no 'Delay' or 'Sleep' function within commands i don't see any way to limit the rate, otherwise we could break the patch functions up and do say the first 50, wait, next 50 etc etc.. although this still doesnt solve the fact that multiple users could be executing the command together.
I already load all data into collections for processing, not viable if it has to be real time, but if a couple of users patch at the same time then its just error after error.
There has to be some form of limit to stop ddos etc but i do feel the rates need to increase significantly as if i'm getting them testing with 1 user, how do we expect to roll this out for multiple.
This particular issue came up when Microsoft premiumized SQL and other connectors in October of 2019. While that particular issue has not come up since, we get daily errors using the SQL connector with table writes colliding or just failing to write altogether. I would say, it's about 99% reliable at the moment. I have 60 active users on a single app.
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