Rate limit is exceeded for mail (V3) connector

[Barbara2]

Hello,

Whe are using the mail (V3) connector in all our flows.

The flows normally work.

However when the flows are executed many times in a few minutes, we are getting the following error for the mail connector:

Statuscode: 429

Message: Rate limit exceeded. try again in 49 seconds. Please see https://docs.microsoft.com/azure/logic-apps/handle-throttling-problems-429-errors for more details.

Any help is welcome. What could we do to solve this problem?

Kind Regaards,

Barbara

[trice602]

Hi @Barbara2 ,

Can you share your flow and a sample flow output please?  There may be an opportunity to put a trigger condition in the trigger to have the flow only fire with something is true and thereby eliminate some of the unnecessary flow runs.

[Barbara2]

Hi @trice602 ,

Thanks for your response.

In fact there is no automatic trigger. We start the flow manually.

It is an approvalrequest flow. This flow is started manually whenever someone has changed a document and want to let the document to be approved.

And whenever a document get's accepted in this flow, we need the mail connector to send  an email.

Now when the flow get's started multiple times in a short amount of time, we have that error for the mail V3 connector.

I found in the doc that there is a limitation for the API calls per connection: 5 calls in 5 minutes.

Maybe this is the problem. Every one is using this flow to start the approval process. So the mail connector is used a lot.

Any idea how we could augment the limitation of 5 calls per connection?

[trice602]

Hi @Barbara2 ,

Please share your flow so I can see the actions.

[Barbara2]

Hi @trice602 ,

The error is for the mail (v3) connector:

The complete flow is saved as PDF in attachment.

I did not expand all actions, as it is a big flow.

[trice602]

Hi @Barbara2 ,

Thanks for sharing.  You mentioned that you use the connector for all flows.  Are there other flows that are triggering (without a trigger condition) that can help you with the rate quota?  As you mentioned, this is being manually started so this particular flow is not the root cause; I am assuming there is one or more flows that are triggering automatically and (most likely) one or more of those flows can be modified to reduce the number of runs.

[Barbara2]

Hi @trice602 ,

In fact all flows are started manually.

Those flows are all identical, the only difference is the library name.

So I do think it has something to do with the mail connector. Per default this connector only retries 2 times. I would like to augment this limitation once for all those mail (v3) connectors, but I do not know how. I know how to do it in the flow itself on each mail (v3) connector.

But I'd like to change the standard rate limit for all mail (v3) connectors.