You’re offline. This is a read only version of the page.
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?
Just an eŃ…ample.
Imagine the connection targets recipient's email jdoe@contoso.com
If To: field is empty, the trigger will handle a message BCCed to jdoe@contoso.com
If To: field contains jdoe@contoso.com the trigger will NOT handle a message BCCed to jdoe@contoso.com
Hi,
I use the When a new email arrives (V3) trigger in my flows but i still don't understand the "To" condition's utility.
Indeed, since the connection already targets the recipient's email, how does entering an email list in this input change the behavior of this trigger?
Could someone explain to me clearly in what case it is used please?
Regards.
"..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.
Thank you!
Doesn't solve the issue on this end.
Same issue here.
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.
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.
Hi
Any solution to this?
Having the same issue with no mail triggering using the connector in Azure Logic Apps.
Brgds
Christian
#1
Tomac
986
Moderator
#2
stampcoin
699
Super User 2025 Season 2
#3
Riyaz_riz11
577
Super User 2025 Season 2
Share
Report
All responses (
Answers (