Need to optimize My Automate flows.

(0) Share

Report

Posted on by ROSEBLACK

205

Dear Experts,

I have a flow.

To day, I'm getting the alerts below.

Can you please help me to optimize My Automate flows so that I can pass the alerts

My Flows

The Alerts

Your flow is executing an excessive number of actions per day and reached 80% of the Power Platform request limit. If the usage grows, further actions may be throttled or slowed down.

Your flow is running too many actions
Your flow has exceeded its Power Platform Requests (https://aka.ms/pa-ppr) limit in the past 24 hours. If this high usage persists, your flow actions may get throttled and slowed down. Power Platform Requests used: 14xxx, Power Platform Requests transition limit: 10000.

Your flow may be performing slow because it’s running more actions than expected.
Throttling events happened for your flow in the past hour.

Thanks in advance.

Regards,

David

Categories:

General topics

I have the same question (0)

All responses (5)

Answers (1)

creativeopinion 10,502 Super User 2025 Season 2 on at

Like (1)

Report

@CU29070737-1 Anytime you use an automated trigger it's always best practice to include trigger conditions. Without trigger conditions your flow will trigger every time an item or file is modified. Without any additional insight it's hard to provide specific recommendations.

In the meantime, add trigger conditions to your flow. Learn how below:

4 Ways You Can Use Trigger Conditions in Your Microsoft Power Automate Flow

Trigger conditions can be set in most flow triggers. These conditions you set must be true for the trigger to fire.

In this Power Automate tutorial, I’m going to show you how to use trigger conditions in your flows to control when your Power Automate flows trigger. If your plan has flow run limits—you can avoid triggering your flows unnecessarily by using trigger conditions.

I’ll cover four different flow examples that would benefit from trigger conditions:

⚡️ Triggering a flow when a column is changed to a specific value
⚡️ Triggering a Flow When an Event Updated or Deleted
⚡️ Triggering a Flow When a New Folder is Created
⚡️ Triggering a Flow When a Specific Email is Received

I’ll also show you a trick on how to easily create the expressions needed and give you a few tips on how to troubleshoot your flow.

IN THIS VIDEO:

✓ Four different flows that would benefit from trigger conditions

✓ What is a trigger condition?

✓ How to add a trigger condition to your flow

✓ How to trigger a flow when a column is changed to a specific value

✓ How to trigger a flow when an event is updated or Deleted

✓ How to trigger a flow when a new folder is created

✓ How to trigger a flow when a specific email is received

✓ How to troubleshoot a trigger condition

✓ How to prevent case sensitivity issues with a trigger condition

✓ How to use the filter array action to easily compose an expression that can be used in a trigger condition

Hope this helps!

Consider giving me a ❤️ if you liked my response!

👉 Level up your Power Automate skills by checking out my tutorials on YouTube
👉 Tips and Tricks on TikTok and Instagram

Was this reply helpful? Yes No
ROSEBLACK 205 on at

Like (0)

Report

Hi @creativeopinion

Thank you for your replying the topic.

Yes, currently when an item or a file is modified in my SharePoint list (less than 70 items) I already included a trigger condition as below. Can you please help to check it's fine?

Was this reply helpful? Yes No
David_MA 12,966 Super User 2025 Season 2 on at

Like (1)

Report
What you list as a trigger condition is not a trigger condition, it is just a regular condition. Trigger conditions are set up in the trigger action under its settings. You can learn about trigger conditions and preventing infinite loops at How to avoid infinite trigger loop in Power Automate

Based on your original post since you don't show how your actions are configured, I need to make some assumptions:

The get attachments action is getting the attachments from an item you hard coded the ID value of and not the attachments from the item or file is modified trigger.

That the add attachment action is attaching it to the item that triggered the flow.

If both of those assumptions are correct, you created an infinite loop. When you add the attachment to the item, it then triggers the flow again because that modifies the item.

Was this reply helpful? Yes No
ROSEBLACK 205 on at

Like (0)

Report

Dear @David_MA @creativeopinion

Below are details of both my actions (the get attachment & the add attachment actions).

Can you please help to check? Thank you so much.

Was this reply helpful? Yes No
Verified answer

David_MA 12,966 Super User 2025 Season 2 on at

Like (0)

Report

Based on your new post, my assumptions were correct. You have created an endless loop. Although, if I understand the flow images correctly, you are adding the attachments from the item that triggers the flow to the item that triggers the flow. This makes no sense and there would be no reason to do this.

If what you were doing made sense and you needed to prevent an endless loop (say you were adding the attachments to a different list), review the information here: https://tomriha.com/how-to-avoid-infinite-trigger-loop-in-power-automate. If you looked at that resource and you didn't understand it, here is another one: Microsoft Power Automate Trigger Conditions: Example-based Guide - Citizen Development Academy.

Trigger conditions go in the trigger action:

I would suggest this for a trigger condition: @greater(triggerOutputs()?['body/Modified'], addMinutes(utcNow(), -15))

This will prevent the flow from triggering if it was already modified within the past 15 minutes.

Also, if this were set up correctly, in the add attachment action, you would use the file content from the get attachment content action and not the body and display name from the apply to each action.

Was this reply helpful? Yes No