Email flow stuck after so many emails

[Alaskan_PBI_guy]

I feel like I run a basic script...  I have 150 different people in my org that have to get a link to a unique report they control. It used to be one script that said "User A gets this email with this link > next step User B gets this email with this link >etc. etc."

It got stuck about half way down, so thought the flow doesn't enjoy running 150+ emails in flow. So told broke it down to 5 flows - alphabetic last name for user to help me put who goes where. I can get A-K to work no issues. L-N has a few where one trigger takes 30+ minutes to do. O-R works fine. Then S-Z it gets stuck on someone in the S every time [not the same person it was the previous attempt either]. Made sure I told the flow to continue on failure, but it just gets hung up and I have to cancel every time because it'll be 10+ hours stuck on one trigger.

I also have the flows scheduled 1 hour apart from each other so they wouldn't overlap on email processing. The other flows take less than 45 min to run total so figured that was safe bet to run them by - still have the same issue though. Any ideas out there to help me understand or find a workaround? [workaround can't be to consolidate into one email with all the links because sadly the org prefers the emails have unique verbiage in each individual one going out].

[wskinnermctc · Accepted solution]

You are probably running into limits of the flow or the Outlook Exchange Server.

Read more about Power Automate Flow Limits for what can be done by flows on an account.

Read more about Outlook Connector Limits for the Outlook connector.

Read more about Outlook Exchange Limits for the Outlook app.

I think it says you can send 30 messages per minute.

4 When outbound message volumes surpass the message rate limit, any excess in message submission will be throttled and successively carried over to the following minutes. This will typically not block the sender's account, but Exchange Online isn't suited to accommodate bulk-mailing scenarios. For this use case, options 2 and 3 here are recommended instead.

[Alaskan_PBI_guy]

I guess your explanation works as an answer?

- I separated the groups into even smaller buckets and separated the runs over 5 different days now and no issues.

Just a shame that is 'says 30 messages per minute' and ' will successively carry over to following minutes'... but it actually doesn't do that. Confirmed E5 license and within the sizing limits mentioned in your articles. No security blocks on the E5 from administrative side. Counted the total number of the bulk-mail scenarios that went out last week and there's 148. So technically, it should do this whole job in 5 minutes. It just 'doesn't want to do it'...