Unanswered

Throttling - but only on sending emails (V3)

(0) Share

Report

Posted on by jleampark

I have built a Request system for my Admin people to handle things like signing up for classes, being reimbursed for travel, etc. There are about 30 different types of requests, each with its own list, form, and workflow.

Flows are starting to get throttled -- but it only seems to be delayed on sending emails (V3).

How can I reduce this (or prevent it altogether)?

The flow goes through a switch based on the Status, sending out an email for a New Request or if it was Assigned or Completed.

Categories:

General topics

I have the same question (0)

All responses (5)

Answers (1)

Verified answer

Sundeep_Malik 6,484 on at

Like (2)

Report

Hey @jleampark

There could be multiple reasons of throttling. Sometimes it's issue of license as well.

But I think in your case it could be you are reaching a limitation of send an email notification v3 action.

This action can only send 100 mails every day.

So as an alternative I would suggest you to use send an email v2 which is of office 365 outlook connector. This can send 900 emails every 60 seconds.

Plus send an email notification v3 action has been performing really bad since last 1 year, it is stopping unexpectedly and many people have complained about it.

So, I would any day suggest send an email v2.

I hope this helps 🙂

Was this reply helpful? Yes No
jleampark 25 on at

Like (0)

Report

Thanks! We were told to use V3 over V2 mainly because of who the email comes from.

V3 says it comes from Microsoft Power Apps (microsoft@powerapps.com) while V2 says the email is coming from me (if I created the flow). With this request system, we didn't want 900 or so employees think I am emailing them about their request.

You haven't seen any workaround for this issue?

Was this reply helpful? Yes No
Sundeep_Malik 6,484 on at

Like (0)

Report

@jleampark

Unfortunately there is no work around for this.

Yes everyone uses V3 for this reason only that it sends email from Power Apps.

One possible workaround could be using a service account.

All the emails would be sent from that service account. Try researching on service account on Google. And I also found some alternatives for you. Check the below videos:

https://m.youtube.com/watch?v=AMl-Sv3O4bk

https://m.youtube.com/watch?v=4hqpDp54-Q4

https://m.youtube.com/watch?v=DQl3Dp-UDgo

Was this reply helpful? Yes No
jleampark 25 on at

Like (0)

Report

Actually, my problem is most likely the limit of 5 emails in 5 minutes for Send an email notification (v3). On a new ticket, two emails are sent -- one to the requester and the other to the Admin office. So, if there are 3 or more requests submitted within a 5-minute period, it's going to throttle.

Microsoft had reports of customers trying to use this notification to send spam, for that reason they lowered the limits to 5 mails per 5 minutes in addition to the 100 mails per 24 hours limit we already have in place. Each email will count as only one API call per connection, even if there is more than one recipient in the To, Cc, or Bcc fields.

So we are now looking at ditching the email notifications altogether and just refreshing the gallery Dashboard on a periodic basis. Admin will just have to get into the habit of checking their Dashboard throughout the day.

Was this reply helpful? Yes No
jleampark 25 on at

Like (0)

Report

I was able to get a Shared Mailbox set up in my Organization for testing.

Am I correct in that V2 emails are "limited" to 300 every 60 seconds and 30 concurrent connections?

Outlook.com - Connectors | Microsoft Learn

Was this reply helpful? Yes No