600 requests per minute per user limit

[PhilD]

Hello!

Can someone help me understand and interpret the implications of this statement found on: Blog > General > Tutorials > Networking > Common Patterns > Performance considerations with PowerApps

<snip from blog post>

Limits

When deploying your app to a large number of user, one has to keep in mind the connectors are throttled. PowerApps currently support 600 requests per minute per user and up to 30 concurrent calls per user. 

</snip>

We are preparing to use PowerApps to dispatch tasks to a team of around a hundred folks using a dispatch app and a separate mobile style app which will be used for each staff member. All of this works very well on a small scale and is easy to demonstrate the value. I am concerned becuase we have never used PowerApps on this broad of a scale before and this limit is not entirely clear to me. I was planning to have the mobile app each staff is running refresh every minute or so. 

Regarding the limitation statement, how can I determine the number of requests? I used Fiddler and can see the HTTP requests made by the app but it only creates a few rows like what is shown below but it is returning a couple hundred items from a SharePoint list (tasks) and another fifty or so from another list (employees). I am thinking that there are more requests than represented here but not sure how to accurately tell.

In theory, the limits are per user so adding more users should not be an issue, only if any single user goes above the limit in a minute. Is this true? Do you think I should be worried about this? 

[PhilD]

Has anyone maybe had some general experience with lots of users on a single app that refreshes on an interval?

I'm not sure how to confirm whether we can expect to have problems without actually deploying (in which case it would be too late).

Any insight or experiences would be helpful... thanks!

[v-micsh-msft]

Hi @PhilD,

Thanks for raising this.

Currently there is no detailed information published for PowerApps implementation, like best practise, or considerations part.

Only App usage report for single Apps available:

App usage report - Monitor how many users are using your App within your organization

For the limits, configuration, see:

Requirements, limits and configuration

Regards,

Michael

[PhilD]

Thanks.

I think without any more verifiable information than this we will need to cancel this project. There is currently a purchased system in place which would be replaced by this power app but I cannot in good faith promise this will work and then have it fail with no backup plan.

It is a shame, because I have a sense that it would work but I can't have the entire project, involving a hundred or more people, be dependent on my sense.

[Reza]

I am trying to get some clarification on that number. In the meanwhile, I feel you should not be concerned about that limitation. That applies to data calls, Calls that are used to get your data rows not internal PA calls. Those call usually have apim in their URL. api.powerApps.com is NOT counted in it.

Thanks

Reza

[Ying · Accepted solution]

Hi @PhilD, the 600 limit is defined per-user per-minute, there is no limits on the number of users using the app. We see PowerApps with thousands of active users; for example one app has over 17k users.  

The 600 limit apply to Connectors endpoint only (that is the URL that have hostnames *. azure-apim.net). Limits don’t include requests with method = OPTIONS, only for method = GET, PUT and POST.

We put a limit on the number of requests per-user per-minute is to discourage unreasonable number of data requests; in general an app making over 600 requests per-minute will likey not have a good user experience.

Thanks,

Ying

[PhilD]

Thanks @Ying, this is the type of information I needed to satisfy the team's concerns. 

If I'm understanding this correctly, it sounds as if one would need to have an extremely poorly designed app to be affected by this limit and it would be likely that the poor performance would be a greater limitation than the actual request threshold.

My apps will be pulling sorted SP lists refreshed every minute to organize task/employees in galleries based on type, status, etc (plain text fields). Essentially providing a mechanism to marry tasks with people, updating the status of each throughout the process. A perfect use case for PowerApps it seems so I didn't want to abandon the project. On the other hand, because this involves abruptly moving away from an existing system (yearly contract), I really need to be sure there will not be any hard stop type of barriers to using this.

I appreciate the information, it helps a lot.

[luuminhvuong93]

@Ying  @Reza  @v-micsh-msft 

Dear PA team,

I plan to have an app that use sharepoint list as back end to store data from Powerapps,

If at the same time 1000 users hit save button on Powerapps, will there be any risks / failure issue ?

[luuminhvuong93]

I have a simple task like this - 700 people to hit the button called "Check In" on PowerApps,

And Patch the results to the SharePoint Lists (which creates a new item for every users). They only have to hit this one time only at the start of the day. But all of the Check-Ins will be done at almost the same time (Like an Attendance Check List)

@Ying   Do you think there will be any potential Failure / Throttle Limits

[Mbruse]

@PhilD 

Did you build this app?

if so, did it go smoothly with so many simultaneous users?

I am considering doing the same.

Mike