You’re offline. This is a read only version of the page.
Hello all,
I have built a flow, which reviews set of rules on every e-mail sent to shared mailbox. This is needed due to client contract auditing purposes.
Rules are not relevant, but just to give you an example, subject and all attachments are reviewed whether they contain specific string. If the string is not there, an e-mail is sent to sender of e-mail that he has breached some rule.
The trigger is "When a new e-mail arrives to shared mailbox V2".
I have just received an e-mail notification, that the operation has been throttled, because flow's operation is hitting an action limit designed to protect the connector service being called.
Is there any possible workaround from your point of view to reduce the amount of actions?
Any advice is very much appreciated.
Thanks,
Majo
Certain actions (like Refresh a dataset [Power BI connector]) have usage limits based on the type of account (Pro/Premium) for the number of times a flow can be run daily. For Pro accounts, the limit is 8 times, and for Premium accounts, it's 48 times. Therefore, please wait for a day to ensure there are no errors with the flow before re-running it
i have received the same error "Looks like your flow's operation is hitting an action limit designed to protect the connector service being called.", but its from reloading BI, any idea?
Hi @fchopo ,
the amount of requests may vary. But we speak about hundreds of e-mails per day. There is around 100 resources and each e-mail sent to the client needs to be checked. So when I receive the notification that the operation throttled, it means that the limit has been reached and no further e-mails are checked on that day?
The flow contains multiple checks:
1. check if the e-mail contains attachments. If it does, check if the name of each attachment contains specific prefix
2. check if the sender is allowed to send e-mail to client (comparing with list of users in sharepoint list)
3. check if the domain of all recipients is either our internal organization or the client - nothing else.
If any of these rules is breached, the sender of e-mail receives an e-mail notification that he does not comply with communication rules. And on top of that he/she is logged to the Breach Log.
I dont know any by heard, but heres some stuff i find useful:
- streamline everything inside loops (You dont need to throw the entire output of a 'get items' action in a apply to each loop to check if a field matches a condition, use odata filter query)
- try to avoid using a lot of variables (especially inside loops), usually its possible to use expressions directly when trying to, for example, update a field
- sometimes you can use first( to grab the first string or record from an array if you know you need that one, rather throwing it in a loop and set a variable
- dont be afraid to experiment with somewhat complex expressions (especially inside loops) to directly grab what you need (its usually possible to 'drill down' using expressions)
Hi @MalyMajo
How many emails do you receive daily in the shared email box?
What are you doing in the flow? (Sending another email or teams message when rules are accomplished, for instance? Creating an item in a SharePoint list?)
According to that we can provide more information on how to overcome the problem.
Currently daily limits for Office 365 users is 10000 requests/day (a request is basically an operation inside the flow)., according to the official documentation: https://docs.microsoft.com/en-us/power-automate/limits-and-config
Maybe you could evaluate buying a specific plans: Updates to the Power Platform request limits | Power Automate Blog (microsoft.com)
Hope it helps!
Ferran
Yes, every action counts towards this limit
I don't know how this works exactly. I think most actions are pooled and counted per user, so basically you get X amounts of calls per license.
Not sure if splitting the flow into a bunch of smaller ones will fix your issue, maybe you will run into it in a different way. Getting flows more efficient is a good idea anyway, and there are some great articles/blogs on how to achieve it
So by action is meant every action in the flow and not the trigger action?
I don't have any nested flows, but the process itself is quite complex.
Does that mean that to avoid this issue I can simply split the process into multiple smaller procedures?
It depends on the efficiency of your flow. There are a great many ways to increase the efficiency of flows and how many actions they used.
For example, nested apply to each loops will greatly reduce the efficiency of a flow and should be avoided
It really depends on what your flow looks like
#1
WarrenBelz
146,645
Most Valuable Professional
#2
RandyHayes
76,287
Super User 2024 Season 1
#3
Pstork1
65,997
Most Valuable Professional
Share
Report
All responses (
Answers (
