"When a new email arrives" not triggering/unreliable

[britishbulldog1]

I have been playing with Power Automate for the last week and seem to be having a bizarre issue. My flow itself is sound, however the trigger seems to be very intermittent. 

I am using the "When a new email arrives (V3)" trigger with no requirements as shown in the screenshot below. However, what I'm finding is when the email arrives in the Inbox - it's not always triggering the flow. It either doesn't trigger or doesn't trigger for about 10 minutes. I am well within the quota and am an E3 customer.

This is more prominent behaviour on emails that are received as 'Send of Behalf' from another user, but this shouldn't have an impact (correct me if I'm wrong). I am loving the Flows experience but this is really putting a dampener on it for me as I'm not finding it too reliable. I have seen forum posts from a couple of years ago with the same issue but no resolution.

My organisation is using Office 365 in a hybrid configuration (mailbox being utilized has been migrated) if that makes any difference at all.

Any ideas on how I can resolve this issue, or any general help/pointers would be much appreciated!

[v-litu-msft]

Hi @britishbulldog1,

I have tested on my side but not find the same issue, the "When a new email arrived (V3)" could be triggered in a few minutes.

Could you please have a test that using the "When a new email arrived" action of Outlook.com connector, it will be more stable:

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.

[britishbulldog1]

Hi @v-litu-msft,

How many times did you test this? The connector is working inconsistently. There have been multiple posts about this in the last day or so.

https://powerusers.microsoft.com/t5/General-Power-Automate/When-a-new-email-arrives-V3-not-triggerin...

I can’t say it’s looking like a coincidence and hope MS fix it soon. Is there a reason behind the Outlook.com connector being more stable?

[v-litu-msft]

Hi @britishbulldog1,

Do you still have the problem today?

I tested it 30 times yesterday, and every email would trigger the Flow.

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.

[britishbulldog1]

Hi @v-litu-msft,

It seems to be performing much better today, no changes have been made to the flow.

I really want to start using the Flow but I don't know if I can trust the trigger to be reliable. 

Were there any reported outages? As mentioned earlier, there were a few blog posts about the trigger concerned.

[sunithav]

Hi,

I'm experiencing the same issue outlined in this post. I have tested flows in two different tenants. The problem is not just with this trigger but other triggers as well like when an item is created, when an item is created/modified. Flows do not trigger at all or trigger after a long wait. Is there any issue with the service? 

Thanks,

SV

[WillJay]

Can confirm reliability issues still exist with the '...email arrives (V3)' outlook trigger. Had a flow triggering okay for a week, then it misses 5 emails, triggers on the 6th and has missed all since. No errors, just not triggering at all.

Have tried deleting and reinserting the trigger, refreshing connectors etc.

For any business case automating the processing of emails this is an unacceptable level of unreliability.

[kushanperera]

There is a known limitation of Office 365 Outlook connector.

Possible solution:

Try filling all filter conditions such as To, From, Cc, Subject...which improved in my scenario. 

From Microsoft documentation: 

The When a new email arrives, When a new email arrives (V3) triggers fire on received emails almost immediately in most cases, but there could be rare occurrences when trigger's delay to fire on new email takes up to one hour.

The When a new email arrives (V3), 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.

Upvote if you found this useful. 

[MichaelURev]

@kushanperera Is this limitation that it won't trigger on emails prior to the last successful run still an issue with the When a new email arrives (V3) trigger?

This means that all emails received while power automate takes its time will be skipped. I'm having trouble where random emails are being missed as well. 

[jw78]

I have similar issue with this britishbulldog1, I tried When new email arrives (V2) and (V3). Seems that V2 is for personal microsoft accounts, coz I could connect my work account with it, so that I could only use V3.