Power Platform Community Forum Thread Details

Hello everyone !
I got a tricky question for you : How do I work around a trigger limitation ?

A little context :
Someone from another team created a flow to get all new email sent to a folder (say Folder Y) of a shared mailbox, check if they have attachments and if yes, copy the file to SharePoint.

So far, so good.
Except, sometimes the rules' execution that moves from a folder to another are slow, or someone had to move manually the email from folder X to folder Y. And, unfortunately, this trigger (When a new email arrives in a shared mailbox (V2) | Microsoft Learn) is based on


 the date and time an email was received.
Moving an email to another folder does not change the received date property value, so the triggers will skip any email that was received prior to the latest successful run.

As stated in the Known issues and limitations with triggers | Microsoft Learn section.

So, to sum up :
Shared Mailbox receives Email1 at 10:52 on October 6th, in Folder X.
Someone from the team moves it from Folder X to Folder Y at 12h30 on October 6th.
The flow won't trigger for this email at 12h30 on October 6th.

How can I workaround this "received date/time" trigger limitation ?

I thought about using conditions, but I'm not sure it will be enough.
Should we be less specific and just use the trigger "When a email is received by a shared mailbox" -if it exists- and then check the folder to tidy all the attachments ?

Thanks a lot, I always appreciate your help !

Categories:

Building flows

Dear A,

There seem to be several options open to you:

Ensure that nobody drags emails into the mailbox ... as you describe the issue with that. Or ensure that they never drag only forward the email to the mailbox.
Put a rule on the mailbox which forwards the email to another mailbox at all times (regardless newly send or dragged). Then put the flow on the new mailbox. You should be able to better 'control' this new mailbox and prevent drag-n-drop actions.
Put a trigger on the mailbox which is set on scheduled time to check all emails in the box and verify this with a checklist (some excel/sharepoint list) to see if you already processed the email before and if not, process it. This would circumvent the drop of emails being missed out.

Happy flowing,

Koen