Power Platform Booster is in public preview. Documentation will always reflect the latest version.

The core concept of API request optimization is that a data freshness of one week is good enough. In the default setup, the load is spread over one week but this can be changed based on your own insights. The default setup is described on this page.

In the default setup:

  • the flow “PP Booster – Flows to process” is run on Saturday.
  • the flow “PP Booster – Apps to process” is run on Sunday.
  • the flows “PP Booster – Apps” and “PP Booster – Flows” are run on weekdays.

Optimization consists of the following steps:

  1. Run the cloud flow “PP Booster – Number of apps and flows”.
  2. Calculate the total number of canvas apps and cloud flows. Take the maximum of the two.
  3. Multiply this number by 3 and add 25% to it. This number is Max-1.
  4. Divide the total number of canvas apps and divide it by 5. Add 10 to this. This becomes the value for the setting: appstopcount
  5. Do the same only then for cloud flows. This will get the value for the setting: flowstopcount
  6. Add both numbers and multiple them times 12. Add 25% to it. This number is Max-2.
  7. The PP Booster account needs to be able to execute at least the number of API requests which is the max of Max-1 and Max-2.

Detailed explanation

Max-1 stands for the maximum API requests in the weekend. Max-2 stands for the maximum API requests during the weekdays.

To optimize the API requests, the goal is to spread the load of the cloud flows “PP Booster – Apps” and “PP Booster – Flows” over the weekdays.

The release contains a cloud flow called “PP Booster – Number of apps and flows”. When this cloud flow is run, the run history can be used to see the number of apps and flows per environment. These numbers can be used to calculate the number of canvas apps and cloud flows.

In both “PP Booster – … to process” cloud flows, there are 3 actions in the “Apply to each” who are always executed. This is the reason for the number 3 in the multiplication.

25% is added to compensate for other actions that are executed in those cloud flows or by other cloud flows that day. This is an estimate and can be different for your situation.

The number 5 in the calculation of Max-2 comes from the 5 weekdays. The number 12 in the calculation comes from the fact that 12 actions are always executed in the “Apply to each”. The 25% is again to compensate for other actions.

The canvas apps are executed under the account of the employee starting it and will therefore not directly count towards the number of API requests for the PP Booster account.

API request optimization is an ongoing activity because the number of canvas apps/cloud flows can change due to additions and clean-up.

Example

There are 100 canvas apps and 500 cloud flows.

Max-1 is therefore (500 * 3) * 1.25 = 1875

Canvas apps > (100 / 5) + 10 = 30

Cloud flows > (500 / 5) + 10 = 110

Max-2 > ((30 + 110) * 12 ) * 1.25 = 2100

Therefore, the PP Booster account needs to be able to execute at least 2100 API requests per day.