Error Server Response Rate limit is exceeded

[Frans_365CH]

I have this runtime error in my app, this was already there before but disappeared spontaneously.
I only see this errror in the app checker, the app works normally. The error is already there at start-up, there is only 1 user. 

I have no idea how to handle this. Too much data traffic cannot be the cause? To many calls to the server? I'm desperate and can use good advice. 

Thank You for anny idea!

Back-End = SQL

[eka24]

it a trial period for the Azure Sql. I had similar experience when my database reached a certain limit in terms of records in my tables. Hope is not the same .

[Frans_365CH]

we have our own servers, so it can't be ... 😉

[Frans_365CH]

Does this error occur if there are too many lookup fields in your app?

[Mr-Dang-MSFT]

@Frans_365CH,

How many lookups are you doing simultaneously?

[Frans_365CH]

Thank you Mr Dang, I am very happy with your help! 

I usually use the lookup for the combo box, Sometimes i have 10-12 lookups in one screen also in gallaries at the same time, see my screenshot. 
But is it not strange that when the app is started this message appears?

what I also find strange is that I have two equivalent apps. One for the tablet and one for the desktop. Only the desktop app give me the error. 

I also did a test to load all tables for the combo box into collections, but it makes my app slow.

your help is greatly appreciated

[v-yutliu-msft]

Hi @Frans_365CH ,

Yes, I think your problem should be related to too many  lookups.

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:

https://veenstra.me.uk/2018/07/17/microsoft-flow-connector-limits/

In your app, since you use lookups in gallery, please notice that:

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 api.

So using many lookups in gallery will increase the number of call a lot.

I suggest you re-design your App to make fewer calls to api per minute.

You should lookup less records (e.g. 50 records) to your SQL table once time, and then lookup the next 50 records, etc.

Here are  similar issues for your reference:

https://powerusers.microsoft.com/t5/Building-Power-Apps/Rate-Limit-is-Exceeded-using-SharePoint-List...

https://powerusers.microsoft.com/t5/Building-Power-Apps/Rate-Limit-Exceeded-SQL-On-Premesis/td-p/185...

Best regards,

[Frans_365CH]

Thank you for your advice, but I don't understand something.

In my home page I no longer have any lookup.

the runtime error is over all other screens, but they are not loaded?

Or....

Are all lookups of all screens executed when starting an app? That is what the runtime error indicates. That can't be true?

[v-yutliu-msft · Accepted solution]

Hi @Frans_365CH ,

These things may lead to loading other screens when you just start the app:
1)the App's OnStart property

2)controls dependent with other screens

I suggest you modify your app.

Try these:

1)Avoid controls dependency between screens

2)Optimize the OnStart function

Use the ClearCollect function to cache data locally if it doesn’t change during the user session. Also, use the Concurrent function to load data sources simultaneously.

3)Use delegation

Use delegatable functions could decrease the depress of deal with data locally

4)Use Delayed Load

Turn on "Delayed Load" in your settings

Please refer this in details:
https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/performance-tips

Best regards,

[Frans_365CH]

The errors are finally gone: I hope my tips can help others

These things were not the cause:

1)the App's OnStart property

2)controls dependent with other screens

I think i have hit the limit of controls:
So I have removed all labels that might be unnecessary. Also the * and error labels. 

----------------

In PowerApps you usually create a view and edit form for each screen. Referring to a gallary to display the record is discouraged, so is a lookup the only option?

If you load the record into a collection you can refer to that record instead of a lookup to the sql server. (Use "clearcollect" or the number will increase)

That way you eliminate a lot of lookups in your app, i did. 

-----------------

My app is not yet ready, I think the only option is to start working with modules

-----------------

You can of course also merge screens for "view" and "edit"
----------------

Thank you for all suggestions and attention.