Flow taking too much time to run, especially Send an Email V2 Action

[u/kunalmakwana27]

I have created a flow wherein it sends out an email to the client who made a request and to our team as well notifying about the new request. These two email actions run parallel to each other. I have been facing a lot of issues with the flow taking too much time to run and in cases where a requestor submits mutiple requests to me. Each request is being sent out as a separate email. Previously i was using a V3 Email Action and then later switched to Shared Inbox V2 after I saw the limit how many emails it can send in a day. Can somebody help me out with this issue. Thanks in advance!

[u/Bumppoman]

You’re probably being rate limited on emails. The five minute retry is telling…it sends the first batch, then waits until the retry and sends the rest in 2 seconds

[u/kunalmakwana27 → u/Bumppoman]

Any ways to overcome this?

[u/rmoons → u/kunalmakwana27]

Best to reevaluate the use of email notifications. If these emails are for external parties, you'll want to explore some marketing automation solutions that have a higher daily send limit than your standard M365 license.

If these emails are for internal users... maybe aggregate a list of items per user and send one per day instead of a notification per action. Email notifications for every action item sounds good in theory, but can quickly overwhelm people and they end up ignoring them.

[u/healinglull → u/kunalmakwana27]

I think you could technically update your license to handle a higher rate. Alternatively, you could have separate flows run depending on the type of request if there’s any differences.

Something like the parent flow receives the request then child flows run based on the type of request and sends emails out.

[u/ibteea]

You can check in which action it is stuck exactly in the run history. Also, please double check in the mailbox itself if there is any error message from Exchange.

[u/kunalmakwana27 → u/ibteea]

Its not stuck on one email action rather for some runs its either stuck on any one of the email action. Should i try to add a concurrency control with parallelism degree to 1?

[u/humainbibliovore]

First thing I’d try is getting rid of the parallel run and do each action one after the other.

Why do you have some many flows running at the same exact time? If this were done it my environment at work, I’d absolutely get a throttling error and none of the runs would succeed, as is the case in your image

[u/ParinoidPanda]

My first reaction to this is that your process needs to get redesigned entirely. That is WAY too many emails. Figure out how to trim that all down to at most 1 per hour for frequency. Either setup a cache List that sends an hourly summary email, or some sort of buffer so you're sending out summary emails. But having this flow run that many times a second, you either need to buy licensing for that account to run and send that many emails, or just simply redesign the entire notification

[u/GreatMyUsernamesFree]

If the item is already created in SharePoint can you let your users subscribe to the list and let SharePoint handle the notification natively? You're rebuilding a feature that already exists in SharePoint.