Two cloud flow licensing options—Process license and for each flow plan (legacy)—each allow 250,000 Power Platform requests for the flow in a 24-hour period. That budget covers all users of the flow combined, and the window is a rolling 24 hours rather than a calendar day.
- Each of the two licensing paths carries the same flow-level allowance: 250,000 requests in 24 hours
- The budget is shared across all users of that flow; it does not multiply with the number of people using it
- The 24-hour window is a sliding one: requests are counted against the previous 24 hours each time the flow runs, so there is no midnight reset
- Premium licenses for individual users are metered separately, with each user carrying their own allowance that does not pool across the team
- Required fields and consistent stage transitions reduce corrective calls, keeping shared-flow usage lower
Why your deal-stage flows need a request budget
Your deal-stage flows run hardest in the final days of a quarter. That is exactly when you cannot afford a flow that runs slowly or stops. Microsoft sets the request limits for Power Platform cloud flows in two time intervals, five minutes and 24 hours. It does this so the ceiling matches how flows are actually used day to day. You can read the full rules on the Microsoft page about requests limits and allocations.
Two licensing paths for a cloud flow carry the same flow-level allowance: a Process license and a for each flow plan (legacy). Each lets the flow make 250,000 Power Platform requests across all users of that flow in a 24-hour period. If your quarter-end flows sit on either of these two options, 250,000 requests is the number you plan around.
The distinction between a shared flow-level budget and a user-level budget shapes how you assign work. Sales ops owners often build one flow that every rep touches, and that flow draws from a single pool. Other steps run under each rep's own license and draw from their personal pools. Knowing which is which tells you where to watch the ceiling as volume climbs toward the close of a quarter.
What counts against the 250,000 requests for each flow
The 250,000 figure applies to the flow as a whole, not to any one person using it. Microsoft says the flow can make 250,000 Power Platform requests across all users of the flow in a 24-hour period when the flow runs on a Process license. The same wording applies to a flow running on a for each flow plan (legacy).
So if ten people in your team trigger the same quarter-end flow, they share one budget. The flow's combined usage counts against one ceiling. This is different from how individual user licenses are metered, where each licensed person carries their own allowance.
That distinction matters for sales ops owners who design one flow and hand it to the whole revenue team. Your flow's budget does not multiply with the number of people who use it. One flow, one 250,000-request allowance.
When a call fails and the flow attempts it again, the second attempt draws from the shared budget just like the first. Failed field writes, timeouts, and repair loops all add to the count. A flow that meets clean input on the first try costs less of your ceiling than a flow that has to try twice, which is why data discipline at the source has a direct effect on how much headroom you carry into the final days of a quarter.
How the 24-hour window actually works
The 24-hour period is not a calendar day and does not reset at midnight. Microsoft says the 24 hours is a sliding window: every time a cloud flow runs, the system looks at requests made in the past 24 hours to decide whether you are at your limit. If your flow fires at 11 p.m. and your heaviest usage happened earlier that day, that earlier burst still counts.
This has a practical consequence for quarter-end planning. You cannot save requests by waiting for a daily reset. You plan against a rolling total that starts climbing as soon as your heaviest run begins.
The sliding window also means your heaviest day and the day after it overlap. If your burst starts in the afternoon of the last day of a quarter, the system still counts requests made at the same hour the day before. Any hour you spend heavily stays in view for a full day afterward, so a burst you launch late in one day can constrain you as soon as the next day's runs begin.
Here is a small comparison of the two flow-level options and what they share.
| Option | Requests in a 24-hour period | Scope of the count |
|---|---|---|
| Cloud flow with a Process license | 250,000 | Across all users of the flow |
| Cloud flow with a for each flow plan (legacy) | 250,000 | Across all users of the flow |
How user-level allowances differ from flow-level allowances
Licenses for individual users are metered separately. Microsoft gives an example where two users in a tenant each have Premium licenses and each user gets 40,000 requests in a 24-hour period. If one of them uses more than 40,000 requests, their flows slow down and do not affect the second user, who has only used 20,000 and still has 20,000 remaining.
That isolation is useful. It means one teammate's heavy data pulls do not eat your budget, and your rush does not eat theirs. When you design a quarter-end process, you can decide whether a step belongs on a shared flow, which draws from one pool, or on a step each user runs under their own license, which draws from their personal pool.
For revenue leaders, this is where architecture meets cost. If the same loop repeats for each of your reps and each rep's step is modest, placing it on a flow-level option concentrates the usage. Placing it on each user's license spreads it. The right choice depends on how often the loop fires and how many people fire it.
Slowing down is the practical result when a limit is reached. A flow that has spent its allowance will run more slowly, and slow automation at quarter end is its own problem. Delays in stage notifications, reminders, and record updates ripple into the work your reps are trying to finish before the period closes.
Lining up deal-stage consistency with request budgets
Consistent deal-stage data protects both your forecast and your request budget. Microsoft's page on business process flows explains that a business process flow helps people enter data consistently and follow the same steps every time they work with a customer. When every rep follows the same steps, your flows encounter fewer retries, fewer failed field writes, and fewer correction runs.
Inconsistent data causes a different kind of request spend. A flow that has to repair a deal record that was moved without required information will make more calls than one that meets clean input. Clean stage transitions at the source reduce downstream traffic in your shared pool.
Your CRM can enforce this at entry. In Pipedrive, required fields stop users from adding or editing items or moving deals until those fields are complete, as the Pipedrive help article on required fields explains. When a deal cannot leave a stage missing the data your flow expects, the flow can do its work in fewer calls.
In Close, the opportunity statuses page describes a stage called Contract Sent, marked as a contract pending or awaiting signature. Naming your stages clearly, and holding deals there until the paperwork moves, gives your flow stable triggers to act on.
Clear stage discipline and required-field discipline work together. One keeps deals moving in order. The other keeps each transition rich enough that your flow does not have to loop back and fill gaps. The result on the request side is a flow that fires once with complete data instead of firing again with a partial record, and every avoided repeat is budget preserved for the work that must run in the final window.
Planning your quarter-end flow volume
A practical planning routine helps you stay inside the 250,000-request flow allowance in a 24-hour period. Start by mapping every step of the flow and estimating how many requests each step fires for each deal. Then multiply by how many deals your team touches in the heaviest 24 hours you expect.
Do the same for the steps that sit on Premium licenses, using the individual allowance Microsoft grants each user. Keep the two budgets separate in your planning sheet. Shared-flow usage and user-level usage are metered apart, and mixing them leads to surprises in the final days of a quarter.
The sliding window means your heaviest day and the day after it overlap. Plan your heaviest automation runs so they do not stack on top of a morning that already spent heavily from the day before.
Staging your automation across the window also helps. Instead of one flow that fires on every field change for every deal, design triggers that fire once for each deal when a stage moves. This honors the intent of a business process flow: one consistent path, one trigger point, fewer repeat calls.
When you estimate, include the steps you did not think of at first. Check with your Power Platform admin which steps, such as notifications, logging and audit writes, are metered against the limit. Approval reminders that fire on a schedule count too. Walk the flow end to end with a request counter's mindset, and you will get a closer figure than one built from the happy path alone.
Checking readiness before you raise the volume
Before you switch on heavier quarter-end runs, walk through a short readiness pass:
- Confirm the licensing path for each flow, so you can state whether it runs on a Process license or on a for each flow plan (legacy) and name its 250,000-request budget plainly
- Confirm which steps run under Premium licenses for individual users, since those allowances belong to each licensed user and do not pool across your team
- Verify required fields at every stage transition, because incomplete records drive extra requests when flows retry or repair
- Name your stages and their entry conditions, so a stage like Contract Sent means one thing and triggers fire predictably
- Estimate your heaviest 24 hours by counting deals, counting steps, and adding a margin for retries inside the sliding window
- Decide which steps can move earlier in the quarter, since pulling non-urgent runs out of the final window preserves budget for what must run then
Each of these checks touches work you may already do. The readiness pass simply asks you to do it with the request ceiling in view.
A quarter-end day in practice
Picture the morning of the last day of a quarter. Your team's shared flow wakes up with a partial allowance already spent, because the window rolls. Your first move is to check which deals will hit stage transitions today and how many steps each transition triggers. Deals ready for Contract Sent go through the same path as always, because required fields were completed before they moved.
Reps running their own steps under Premium licenses draw from their personal allowances. One rep's heavy data pull cannot slow another rep who has budget left. The shared flow's pool stays intact for the transitions that must run for the whole team.
If you had planned the day without the sliding window in mind, the shared pool might have run out mid-morning. Because you planned against a rolling 24 hours, you can see it coming and hold non-urgent runs until traffic clears.
By afternoon, the deals that needed a final push are already through. The flow slows only if you pushed it past its ceiling, and you did not, because you held back the runs that could wait. The next morning, some of the day's spend still sits inside the window, so the first hours of the new period run tighter than a calendar-day model would predict.
Related guides
Questions revenue leaders ask
Does the 250,000-request budget reset at midnight? No. The window rolls, and the system checks requests from the previous 24 hours each time the flow runs.
Can two flows share one budget? No. The 250,000-request allowance sits on the individual flow, whether it runs on a Process license or a for each flow plan (legacy).
What happens when a single user runs past their own allowance? Their flows slow down. Other users in the tenant with their own allowances are not affected.
Do required fields help with requests at all? Yes, indirectly. When deals cannot move without complete data, your flows make fewer corrective calls during stage transitions.
Where do I confirm my own flow's licensing path? Microsoft's page on requests limits and allocations lists the options; your Power Platform admin can confirm which license each flow carries.
The sources above set the limits and the window. They do not state how many requests a particular deal-stage flow will need in your environment. Ask your Power Platform admin for usage data on your own flows before you raise quarter-end volume.