Answered

Send an email notification (v3) causes Internal Server Error

(3) Share

Report

Posted on by AM-13092321-0

Hi,

The "Send an email notification (v3)" action stopped working for me since yesterday and I created a simple flow to test the action out. Across all my environments they all resulted in Internal Server Error with the following message:

The given key was not present in the dictionary.
at System.ThrowHelper.ThrowKeyNotFoundException()
at System.Collections.Generic.Dictionary`2.get_Item(TKey key)

Any clue?

Categories:

Business Process Flows

I have the same question (0)

All responses (8)

Answers (1)

BW-27121945-0 2 on at

Like (0)

Report

Send an email notification (v3) causes Internal Server Error

Unfortunately I can't offer any assistance, but my organization has been having a similar Internal Server Error with the Send an Email Notification (v3) connector. Your issue suggests that this might be a Microsoft problem rather than something internal to either of our organizations.

Was this reply helpful? Yes No
AT-27121946-0 3 on at

Like (2)

Report

Send an email notification (v3) causes Internal Server Error

Having the same Internal Server Error issue with my flows with the same connector. It started on 12/24
One workaround is to change the connector to the "Send an email from a shared mailbox (V2)" connector for Outlook 365

Was this reply helpful? Yes No
Suggested answer

Pstork1 68,330 Most Valuable Professional on at

Like (0)

Report

Send an email notification (v3) causes Internal Server Error

Try using the Office 365 Send an Email action instead. Microsoft stopped enabling the mail service in New Tenants a couple years ago. That may be the problem. See the note under limitations in this article. Mail - Connectors | Microsoft Learn

----------------------------------------------------------------------------------
If this Post helped you, please click "Does this answer your question" and give it a like to help others in the community find the answer too!

Paul Papanek Stork, MVP
Blog: https://www.dontpapanic.com/blog

Was this reply helpful? Yes No
AM-13092321-0 10 on at

Like (0)

Report

Send an email notification (v3) causes Internal Server Error

It doesn't look like the problem is related to the Known Issues and Limitations but I do see the note section that Paul was referring to and the Throttling Limits on the same page is concerning too.

Correct me if I am wrong but I feel that the Office 365 Send an Email action is more suitable for flows under Personal Productivity, as these flows are sent using my O365 account (accessible under Sent Items). For organizational production flows, the Send an Email Notification action seems more appropriate as it won't flood my personal outbox with emails with content that I am not supposed to have access to. But it looks like Microsoft is on their way ditching this action making it less than useful now?

Was this reply helpful? Yes No
odd 4 on at

Like (0)

Report

Send an email notification (v3) causes Internal Server Error

This began on the morning of Dec 24, 2024 in our organization. We are GCC (low). One coworker noted that she didn't receive her weekly "X of your flow(s) have failed" email from Microsoft Power Automate, which would indicate that it has stopped working at the level of Microsoft Corporation, possibly. Hopefully this gets fixed ASAP.

Was this reply helpful? Yes No
AH-30122112-0 3 on at

Like (0)

Report

Send an email notification (v3) causes Internal Server Error

I am also a GCC tenant, and all of my flows with Email Notification (V3) are failing with the same errors.

Was this reply helpful? Yes No
Verified answer

NS-30121613-0 11 on at

Like (1)

Report

Send an email notification (v3) causes Internal Server Error

It is working now. 12-31-24

Was this reply helpful? Yes No
AM-13092321-0 10 on at

Like (0)

Report

Send an email notification (v3) causes Internal Server Error

I am now unable to create new flow with the "Send an email notification (v3)" action. It would say "Create simple connection failed".

Was this reply helpful? Yes No