Answered

Operation throttled due to action limit

Like (0) Share

Report

Posted on 21 Mar 2022 14:47:19 by MalyMajo

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

I have the same question (0)

Summarized by AI

AI generated content may be incorrect

Did you find this summary helpful?

All responses (9)

Answers (2)

Verified answer

KvB1 1,596 on 21 Mar 2022 at 16:42:18

Like (1)

Report

Re: Operation throttled due to action limit

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)

Was this reply helpful? Yes No
Verified answer

KvB1 1,596 on 21 Mar 2022 at 16:10:51

Like (2)

Report

Re: Operation throttled due to action limit

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

Was this reply helpful? Yes No