cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
ChrisHH
Level: Powered On

Connector throttle limit workaround needed

Hey everyone,

 

I'd really appreciate some feedback on this as my Microsoft Support ticket hasn't been responded to in 4 days and it's business critical.

 

We have an issue where my application is being used by around 30-40 users and our MySQL connector is hitting a 94% success rate (shown in the PowerApps Analytics page). This is resulting in issues within the application such as incomplete patches. We believe that the issue resides in the throttle limit for the MySQL connector which is 300 calls every 60 seconds.

 

We have an idea that could work, but in practice is quite tricky. Could we use another or multiple MySQL connections (using the same Data Gateway) within the app and have the application determine dynamically which one to use? You could store it as a variable which then is used when collecting and patching. We are only using the connection to collect on within the app (no hardcoded fields with it as a data source) and patches.

 

There are a number of tables from MySQL being used, so I would need to create various data sources per table, but my question is is this possible? or is there a better way?

 

Thanks for reading and any feedback is appreciated.

 

Chris

 

 

 

4 REPLIES 4
Community Support Team
Community Support Team

Re: Connector throttle limit workaround needed

Hi @ChrisHH ,

Do you want to add multiple connections to your MySQL table from your app, and then have the app determine dynamically which one to use within your app?

 

If you want to add multiple connections to your MySQL table from your app, and then have the app determine dynamically which one to use within your app, I afraid that there is no way to achieve your needs in PowerApps currently.

 

Currently, within PowerApps, there is no way to have the application determine dynamically which one connection to use.

 

If you would like this feature to be added in PowerApps, please submit an idea to PowerApps Ideas Forum:

https://powerusers.microsoft.com/t5/PowerApps-Ideas/idb-p/PowerAppsIdeas

 

Best regards,

Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
ChrisHH
Level: Powered On

Re: Connector throttle limit workaround needed

Hi @v-xida-msft,

 

Thanks for the response. Yes, the idea would be to have multiple data connections available but by using a formula we would assign one of the data connections as a variable which would be used in our ClearCollects and Patches. This would split the userbase between connections so we would be less likely to hit an API Calls limit.

 

I appreciate the comment that my solution isn't viable at the moment, however, is there any other way that we can resolve the connector throttle limit problem? It is crucial to this workstream that this connector is working properly.

 

We are currently attempting to reduce the number of calls to MySQL, but if you have any other suggestions, we'd love to hear them.

 

Many thanks,

 

Chris

Administrator
Administrator

Re: Connector throttle limit workaround needed

Hi @ChrisHH how are you progressing with this? Was support able to assist any further?

 

@TopShelf-MSFT 

ChrisHH
Level: Powered On

Re: Connector throttle limit workaround needed

No help from support, however we have found our own work around.

 

Since we are only using the data connection to 'collect' from and 'patch', we have created 2 different connections to the same source which through testing seem to have their own API limits. Therefore at the start of our app, each user is assigned to a connector randomly and every reference to MySQL is a switch statement to determine which connection the collect or patch statement should use.

 

Seems to be working well so far!

Helpful resources

Announcements
firstImage

Watch Sessions On Demand!

Continue your learning in our online communities.

SecondImage

Follow PowerApps on Twitter

Stay Up-to-Date by following PowerApps on Twitter

Top Community Contributors for July 2019

Top Community Contributors for July 2019

Let's thank our top community contributors

Power Platform 2019 release wave 2 plan

Power Platform 2019 release wave 2 plan

Features releasing from October 2019 through March 2020

FirstImage

Power Platform World Tour

Coming to a city near you

thirdimage

PowerApps Community User Group Member Badge

Fill out a quick form to claim your user group badge now!

FourthImage

Join PowerApps User Group!!

Connect, share, and learn with your peers year-round

FifthImage

Dynamics 365 and Power Platform April 2019 Release notes

Features releasing from April 2019 through September 2019!

Users Online
Currently online: 39 members 4,077 guests
Please welcome our newest community members: