Flow exceeds daily runs limit – The flow exceeded the number of allowed executions for a day.

Power Automate enforces a daily run limit based on the user’s license type. When a flow exceeds this limit, it stops running and cannot be triggered until the next day when the limit resets.

This guide explains:
Why the daily runs limit error occurs.
How to check and monitor flow runs.
Methods to optimize and prevent exceeding daily limits.

---

Step 1: Understanding Daily Run Limits in Power Automate

1.1. Flow Run Limits by Plan Type

Power Automate limits daily executions based on the user’s plan type:

Plan Type	Daily Run Limit
Free Plan	750 runs/day
Microsoft 365 Plan (Standard)	2,000 runs/day
Per-User Plan	Unlimited (but API limits apply)
Per-Flow Plan	Unlimited (with fair usage limits)
Power Automate Process Plan	Higher limits for enterprise

• When a flow reaches its daily limit, it stops running until the next day.
• If multiple flows are owned by the same user, they share the daily run limit.

---

Step 2: Identifying the Issue

2.1. Check Flow Run History

1. Open Power Automate (https://make.powerautomate.com).
2. Click on My Flows → Select the affected flow.
3. Go to Run History → Look for failed runs with an error message: pgsqlCopyEditFlow run limit exceeded. Try again after 24 hours.

2.2. Check Flow Usage in Power Platform Admin Center

1. Go to Power Platform Admin Center (https://admin.powerplatform.microsoft.com).
2. Click on Analytics → Power Automate.
3. Review Run Volume and Execution Trends.
4. Identify which flows are consuming the most daily runs.

---

Step 3: Resolving the Issue

3.1. Reduce the Number of Flow Triggers

If a flow is triggering too frequently, reduce unnecessary runs:

• Modify Trigger Conditions – Ensure the flow only runs when necessary.
• Increase Recurrence Interval – If using a Scheduled Flow, run it less frequently (e.g., every hour instead of every minute).
• Use Delay Actions – Add a delay to prevent multiple triggers in a short time.

Example: Apply a Trigger Condition

Modify a trigger to activate only when necessary:

1. Open the trigger action (e.g., SharePoint trigger).
2. Click Settings → Trigger Conditions.
3. Add a condition like: @equals(triggerBody()?['Status'], 'Approved')
4. This ensures the flow only runs when Status = Approved, reducing unnecessary triggers.

---

3.2. Optimize Loops and Reduce Flow Runs

If a flow processes multiple items, reduce executions:

• Batch Process Items Instead of Single Runs – Use bulk processing instead of running the flow for each item.
• Use Apply to Each Efficiently – Enable parallelism to speed up execution.
• Filter Data Before Fetching – Retrieve only relevant records before processing.

Enable Parallelism in Apply to Each

1. Open the Apply to Each loop.
2. Click Settings → Enable Concurrency Control.
3. Increase the degree of parallelism (e.g., 20).

---

3.3. Limit the Number of Users Who Can Trigger the Flow

If multiple users trigger the same flow, it reaches the daily limit faster:

• Restrict access to specific users or groups.
• Use a service account to control execution.
• Require admin approval before running the flow.

---

3.4. Split Large Flows into Multiple Flows

Instead of one large flow, break it into smaller sub-flows:

• Use Child Flows – Move intensive processing to a separate flow.
• Create separate flows for different tasks instead of one large flow.

---

3.5. Upgrade to a Higher Power Automate Plan

If your automation requires more flow executions, consider upgrading to a Per-User or Per-Flow Plan for higher limits.

1. Open Microsoft 365 Admin Center (https://admin.microsoft.com).
2. Navigate to Billing → Purchase Services.
3. Choose Power Automate Per-User Plan or Per-Flow Plan.
4. Assign the new plan to the user or flow.

---

Step 4: Advanced Troubleshooting

4.1. Use Azure Logic Apps for Higher Execution Limits

If your automation requires higher daily executions, consider Azure Logic Apps, which support:
✅ Higher flow execution limits
✅ More advanced scaling options

---

4.2. Use Power Automate RPA (Robotic Process Automation)

For UI-based automation, consider Power Automate RPA, which does not consume standard flow runs.

---

Step 5: Preventing Future Flow Run Limit Issues

5.1. Best Practices for Flow Optimization

Reduce trigger frequency – Use conditions to trigger flows only when necessary.
Optimize loops and batch processing – Process data in bulk instead of running multiple flows.
Limit unnecessary data retrieval – Use filtering and pagination.
Use variables to store data – Avoid redundant flow runs.
Monitor flow usage in Power Platform Admin Center – Track trends and identify overuse.

5.2. Set Up Flow Usage Alerts

• Go to Power Platform Admin Center.
• Set up alerts for high flow usage to detect issues before hitting limits.