Flow missing candidate emails

[PatrickK]

I created a workflow using the "Save my email attachments to a SharePoint document library" template. I set the IsFromFilterApplied to True and included a valid email address in the Check From Email condition. Following that, there are two more conditional checks. If the first conditional check is true, the attachement goes to SharePoint folder A. If not, but the second conditional check is true, the attachement goes to SharePoint folder B. If neither is true, the workflow ends and the attachment is not saved.

The Flow Checker reports no Errors or Warnings, and the flow works properly most of the time. However, there are times where MS Flow just seems to completley miss candidate emails (the email has an attachment and is from the specified sender). It's not that email is recognized but mis-processed. The email doesn't even have an entry in the Run History. In fact, the sender always sends two emails at the same time, one has an attachment that goes SharePoint folder A, the other has an attachment that goes SharePoint folder B. In one instance, only one of the two emails was recgonized (Run History record created - run was a success with the attachment being loaded to SharePoint). The comapnion email was not even acknowledged by Flow.

Aside from completely missing candicate emails, all other emails that have Run History records are accurate. The flow recognizes emails with attachments that are not frrom the sender and terminates immediately. All emails with attachments that are from the sender are properly processed. So the only issue here is not recognizing and processing candidate emails.

Any thought on why this might happen?

[v-litu-msft]

Hi @PatrickK,

Is this trigger When a new email arrives?

What's the condition for your Flow will be triggered? Whether in your trigger have some special Subject filter so that some email will be intercepted?

Best Regards,
Community Support Team _ Lin Tu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[PatrickK]

Hi @v-litu-msft 

The trigger is when an email with attachment hits my inbox. When triggered, the first conditions checks to see if the email with attachment is from Sender X (a sytem email address, not a person's email address). If this condition is True, there are two more conditions that parse the subject line.

Trigger: email with attachment hits my inbox

Condition 1: Is email with attachment from Sender X?

True: Go to Condition 2

False: Terminate

Condition 2: Does subject line contain "PDF"?

True: Save attachment to SharePoint folder A

False: Go to Condition 3

Condition 3: Does subject line contain "XML"?

True: Save attachment to SharePoint folder B

False: Terminate

[v-litu-msft]

Hi @PatrickK,

I have tested on my side send two emails at the same time,but not find the same issue.

How often does this happen to you?

This could be an occasional issue in Outlook service.

Best Regards,
Community Support Team _ Lin Tu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[PatrickK]

Hi @v-litu-msft,

Sorry that I couldn't reply yesterday.

For the first 2 weeks, it missed over 50 percent (46 out of 88 candidate emails). 

Yesterday was much better, it missed only 4 out of 30. However, I noticed later that I had four failures, and each failure correspond to what I had thought was a missed email. So really, yesterday it created 30 Run History events for 30 emails (Yey! 100% success at recognizing candiate emails). But I am a liitle confused by the error message in the failed runs:

---

Error
Action 'Create_file' failed

Save Conflict
Your changes conflict with those made concurrently by another user. If you want your changes to be applied, click Back in your Web browser, refresh the page, and resubmit your changes. clientRequestId: e559ecbd-201f-41b3-b049-191a92790650 serviceRequestId: 91b9fc9e-40b2-9000-f0e7-c0e15db5c8c1;91b9fc9e-30b6-9000-f0e7-c727bead18e1

---

Thanks!

Patrick

Could this error be caused by two emails trying to write to the same SharePoint folder at the same time?

[v-litu-msft · Accepted solution]

Hi @PatrickK,

So the issue that missing email has been solved by itself, it may be caused by the upcoming of Outlook connector: office-365-outlook-connector-important-upcoming-changes

And two emails trying to write files in the same SharePoint folder at the same time may cause conflict. You can create a random delay time, such as 0-10 seconds to prevent the Flow create the file at the same time.

Best Regards,
Community Support Team _ Lin Tu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[PatrickK]

Thanks, @v-litu-msft !