Unanswered

Send an Email V2: Error Trap

(0) Share

Report

Posted on by abc 123

789 Moderator

When using the 'Send an Email V2' action, there doesn't appear to be way to setup error trapping. For example, a malformed email address.

For comparison, when a 'Run a Child Flow' action is used, the Dynamic Content will show properties of that Action that are returned. The 'Send an Email V2' has no presence in the Dynamic Content.

That said, when the 'Send an Email V2' is executed and fails, I've found that the "x-ms-apihub-cached-response" will be False. I want to be able to query this value to denote an email failure, but don't know how to refer to it, as 'Send an Email V2' does not become an Output.

What is the proper way to perform this error trap?

Categories:

Building flows

I have the same question (0)

All responses (4)

Answers (0)

Tristan_D 405 on at

Like (0)

Report
Copy link

Link copied!

Hi @GDSI ,

Quick question, are you trying to test any email or only mails from users located in your tenant (Entra ID) ?

T

Was this reply helpful? Yes No
abc 123 789 Moderator on at

Like (0)

Report
Copy link

Link copied!

Whether I enter my work email address or my gmail address in the To section, neither will cause it to have a presence in the Dynamic Content, such that I can test against it as an Output.

Where are you headed with this question?

Was this reply helpful? Yes No
Jordan-Ryan 112 on at

Like (0)

Report
Copy link

Link copied!

Have you thought about putting it inside a Scope then having a failed step after to check for any errors?

Was this reply helpful? Yes No
abc 123 789 Moderator on at

Like (0)

Report
Copy link

Link copied!

Have you tried putting a malformed email address in the To and run it? It completes successfully, so, in theory, the Scope won't know that it's failed, when the Action reports back a Success when there NO way to trap for the failure. (I'm dizzy.)

Today, I did find where the failed Action emailed the Developer user that the email failed to send, but I'd really LOVE to trap that an Automated Process Email failed on my terms, not the Flows.

Was this reply helpful? Yes No