Having an issue with When a new email arrives (V3) trigger here this morning. It just won't trigger consistently, if at all. I've tried in two separate customer environments with the same result. It's triggered a couple times on each, but with no set time frame, and it didn't trigger on every message received in that time frame. For instance, I sent 4 emails at the same time to the monitored mailbox. 20 minutes later, I see the flow ran once. One has gone for over an hour without triggering, I've received about 2 dozen emails in that time.
I have an identical test flow that I created back in February that's doing the same thing and is working. Literally identical. Only difference is V3 uses the new API method to connect
Both tenant accounts I tried with have a full E3 license. Both have many 'When a new email arrives in a shared mailbox' flows that are working just fine.
I'm not getting any errors.
I've tried recreating the flow and recreating the connection.
My flow is literally just two steps here while I test
Tried it with and without a To defined, as well as trying different folders.
Is anyone else having an issue with this?
Hi @SCTdan ,
Do the emails you use for testing all have the same content and are sent using the same email address?
I noticed that you configured the To field, which may filter out some messages and not trigger Flow.
I did a similar test on my side, but Flow can be triggered normally.
I am having the same issue that started today. Prior to about 6 hours ago the "when a new email arrives" trigger was working properly, with hundreds (if not thousands) of flow runs triggered over the past month or so. Then today it stopped working, or will only work very sporadically (once every 5 or 10 emails).
I've done a bunch of testing including creating a brand new flow using that trigger, with no conditions (to/subject/attachments,etc.) and it is not working either. If I turn off the flow, send an email, then turn it back on, it will pick up the emails that arrived when the flow was off, but there is no way I can get it to pick up emails that are arriving while the flow is on.
Due to some legacy systems we use where an email is the only notification we have to trigger a process flow, this is a very important trigger for our org. Hopefully we can get this solved asap!
I tried both with and without the To field configured yes. Emails had varying content, but the most basic ones were just test / test as the subject and body.
How many tests did you do? Again, it will trigger occasionally.
Hi @SCTdan ,
I also did a lot of tests today. I often use this trigger when dealing with other problems, but Flow can be triggered normally.
This is Flow run history:
@DKassian , we are currently unable to confirm if this is an issue and not able to provide a suitable solution to your current problem. If this issue has affected you greatly, I suggest you contact support for further assistance.
I have been having the same issues earlier this week. Has a solution been found? I have tried implementing a flow that releases the emails on a staggered manner but some of the emails are still occasionally missed.
I too am having this issue, I had just created a flow to save email content on SP but so far I am only able to save emails that I create (to test) and move onto the trigger email subfolder. Other emails from other addresses trigger the flow. I did 3 tests. Test 1: a coworker sent me a test email with "test" as the content, I was able to trigger the flow when I moved to the trigger folder, but i was not able to trigger the flow from other emails from the same user. Test 2: I tried to trigger with email from a different email but no trigger, I then copied all the content and again, created an email and sent it to myself, I was able to trigger the flow when i moved this email to the folder. It only seems that my email triggers the flow, but the fact that my coworker email also triggered does not make sense.
If you are having the same issue as I did, then I found a solution and the reason why. This is from a Microsoft doc. "The When a new email arrives (V3), When a new email arrives in a shared mailbox, When a new email arrives in a shared mailbox(V2), and When a new email mentioning me arrives (V2) triggers are based on the date and time an email was received. Moving an email to another folder does not change received date property value so the triggers will skip any email that was received prior to the latest successful run."
What I did was go through the Flows Templates and used the template called, "Activity record for incoming emails in SharePoint with specific subject". I modified it slightly at add more columns, and I changed the condition to "Subject" "does not contain" "test". I used test because emails that I plan to use for this flow will never have "test" as their subject.
"..based on the date and time an email was received. Moving an email to another folder does not change received date property value so the triggers will skip any email that was received prior to the latest successful run."
This is what I needed to know! Thanks so much. The flow does trigger for anything newly received so I have removed my 'to' criteria to address my testing and backlog and then will reimplement the criteria for day forward and real-time running.
Learn how to create your own user groups today!
Check out the new Power Platform Community Connections gallery!
Join us, in-person, December 7–9 in Las Vegas, for the largest gathering of the Microsoft community in the world.