Trouble shooting email not being sent with Office365Outlook.SendEmailV2

[IncursioML1]

Hi All

I have updated a canvas app's functionality of Office365Outlook.SendEmail to the Version 2 one.  Should I remove the connection of Outlook and make another connection again?

What seems to be happening is that this trigger (it's on a select event of a button) doesn't seem to always work for specific people.  Is there any type of audit trail or log that I can see in which the email actually has gotten sent?  Is there a throttle limit?  I don't think we're even looking at more than 1 request per day.

Since part of the button's event is to submit a new record to a SharePoint list, I'm debating to fire off the email with Power Automate instead since it's a challenge to figure out what's going on with the SendEmailV2 function through PowerApps.  At least with Power Automate there will be the failed/success run history.

How are other users trouble shooting the Office365Outlook.SendEmailV2 function to ensure that the email is being sent?

I know when I go into a session mode while editing the canvas app I can see the ins/outs but what about when users are using the canvas app in which I'm unaware?  

Any feedback would be appreciated.

Thanks

[TheRobRush]

I have never had an issue with the email sending (apps at my company send at least 20 or 30 emails daily to mailing lists of up to 40 people and never fail) using that connector. Are there any differences between people using the app and failing and those who use it successfully? Can you maybe try from your own company account outside of powerapps try and email a known email that fails via powerapps and see if it fails outside that environment as well? If these emails that are failing are external emails to your company its possible their spam filter is just rejecting it (I know I switched one of my business emails for a specific industry to a different provider because the main company it deals with had issues their server autorejecting stuff that originated on MS servers - massive insustry provider and they emailed our a warning to all their clients who used it)

If these are internal company email addresses you might want to share your code with us so we can see if there's something slightly off that could cause it

[IncursioML1]

Ok so I had the user invite me to the app session as a test run and I found out what's happening.

We have a SharePoint List that email addresses are stored in which the app connects to.  It turns out somebody made a mistake on that SharePoint List and had a bad email address in between user sessions.  The app did as much as it could but based on the test run, the email didn't submit and that bad email address was the culprit.  When I looked at the response of the SendEmailV2 the below screen shot is the error.  "All recipients must be resolved until an email can be submitted."

I guess I have no idea how to go around this since part of the email goes to external contacts and some to internal.  Internally I could check the email against our active directory or email server (which I think there's a connector to that), but externally what happens if an email can't find recipient?  Or does the SendEmailV2 function not care if it's external and only cares if internally in order to successfully submit?

The doc doesn't really say much on this.

https://docs.microsoft.com/en-us/connectors/office365/

[TheRobRush]

Other than fix the error in the sp list email, and hope it does not happen again, I suppose you could pivot from having all the emails on a cc (is that how your is currently set up? to looping through the list and sending a seperate email to each? not sure because i have never encountered this issue before , but maybe that would let the other emails send? I made a mockup on my side where first 2 emails were random numbers and letters @a fake domain, then third one with my email and pushing the button, third email still arrived in my box, so maybe thats a solution

[IncursioML1]

Yes there could be multiple CC's so there's a concatenate function utilized for this alongside the semi colon separator in the CC portion of SendEmailV2.  I may have to try your approach to separate it but it would be nice to just have it all go in one email swoop, but at least that way the email will still send.

Thanks!