I have created a flow to monitor a shared mailbox for emails from specific sender and containing attachments to upload the attachments to SharePoint document library and as next step to send email notifications to relevant accounts with details about the upload.
So far so good - the flow works and 99% so far no issues. The emails are received once a day, mid day and the attachments uploaded to SP. Cool.
Until I noticed that the flow did not upload files for Saturday, Sunday and today as well.
Happens that over the weekend our organisation had an Exchange problems which accumulated a que of unsend emails, most of which seems were send today.
So today the mailbox in question received 2 emails with above conditions at almost the same time - like back to back, seconds between them.
I checked the flow history and the flow run twice today, reporting success:
But no attachments were uploaded and no notifications were sent for both runs.
When looking at the 'Yes' branch I see the 'Create file' and 'Send and email notification' actions are dimmed:
IMHO, I think possibly the cause is because the emails were received back to back - the flow started on the first email, then immediately started the second one and crashed or similar... am I right?
So my question is - how can I prevent something like that happening in the future. Especially if I need to build similar to other shared mailboxes...
Any ideas? Perhaps add some pause between flow runs for back to back emails issues? How? Or something more exotic?
Thanks in advance. RS
Any Idea how to delay processing second email (or more mails), when they arrive together?
Like process first email, pause to finish, then next, pause, next, pause to complete, next, pause etc...
I was reading some posts and wander if I can add "Pause" action after the last action of my flow - "Send" email..as per this: https://powerusers.microsoft.com/t5/Building-Flows/Delay-the-flow-for-given-time/m-p/1223241#M140641
Solution by @RobElliott
Is that going to solve my problem?