We are experiencing issues with the Office 365 connector failing I was wandering if someone else had experienced / had some advice.
We have a mailbox, fully licensed E3 with Flow2 also added. Each morning our reporting software emails about 150 reports to the mailbox and the flow is set to take the attachment and move it to various SharePoint libraries.
This has been working for some time, but over the last week or so it only processes some of the emails, say 90 then the rest fail at the "When new email arrives" step reporting "The resource you are looking for has been removed, had its name changed, or is temporarily unavailable."
We contacted support who originally said recreate the connection, worked for a couple of days but now is getting worse. Contacted them again who suggested adding a Flow2 license which have done and still getting worse.
This is happening across 5 of our mailboxes set up for this, and one of them it happens every day - and once it has lost "connection" every check of the mailbox from then on fails until we rebuilt it.
Any advise appreciated.
After much testing we have been able to confirm that all our Flows, despite the fact that are each bound to an account with a Microsoft Flow 2 license attached are experiencing this problem.
If I take one mailbox / flow as an example - each morning our reporting solution emails the mailbox about 150 emails over a ten to 20 minute period, each containing an attachment.
The Flow is meant to take the attachment and save it in a designated SharePoint 365 document library.
What we have found is that it will only process some of them, today it only processed 70 of the emails that were sent. The emails are in the mailbox, but at some point the Flow begins failing on the "On New Email Trigger" with the error "The resource you are looking for has been removed, had its name changed, or is temporarily unavailable."
Once this starts no more Flows will process, each check will continue to fail every minute until we delete the Outlook connection and recreate it.
We have rebuilt the flow from scratch, rebuilt from templates, removed and re-assigned licenses - everything we can think of but it still occurs - the flow only works for some of the emails and stops working every day.
This is causing a lot of issues as we have been successfully using these Flows for a year to delivery our reports to key document libraries in SharePoint, and I cant see how the system cannot be handle 150 emails without crashing.
Screenshot 1: Once the flow starts failing, every subsequent check of the mailbox fails:
Screenshot 2: Error on the On new email event, all it says is the resource is unavailable, starts randomly whilst processing emails:
Screenshot 3: The on new email trigger, it is unmodified, the stock entry when you pick a template. The flow fails at this step, it doesnt even get to the next action of processing the attachment.
The issue seems to be related to the limit in amount of received emails. When the amount of received emails more than the limiting amount, the issue would occur.
I will post this issue to my product team, if the issue is solved, I will reply you here.
I have searched everywhere I can and cannot find any referrence to an email limit, and am suprised that an enterprise solution such as Microsoft Flow would crash completely if there were > 70 emails to be triggered on, especially as you removed email enabled lists from SharePoint - something we had running for 10yrs processing a thousand emails a day.
I you could advise, I have a a second support call open - (118010117388661) but been 12hrs with no response. I need to understand if there is a limit and what the limit is and if there is a work around.
I didnt know whether changing the Flow to some a Scheduled Get Emails like below might work?
Just to update in case anyone is watching...
Submitted a support call via Office 365 - took over 24 hours for someone to get back to me, grant it was New Years day when I logged it. They advised that they were not aware of any reasonable limitation in the number of emails being sent & triggered.
Today, out of the blue, all our flows (6 different mailboxes, each with E3 + Flow2 licenses) started working again, in fact due to an on premise mistake we actually sent the reports out twice, so one Flow triggered 341 times over a half hour period.
Support advised they have done nothing, in fact they have been "researching" for the last 24 hours - its now about 50 hours since I logged the call with no real feedback other than asking me to explain the problem.
I am challenged by experiences such as these - these features are heavily promoted, often replacing decomissioned alternatives, one cannot blame an organisation in trusting and embedding business processes in them.
But as they are Enterprise Solutions they need to act and be supported a such. They cant just randomly fail for 3 weeks, fully fail for 4 days and then start working again with no-one able to say why.
Sorry for my rant but I only have 1000 users and I have ones affected by problems in Flow, Exchange, Teams and PowerBI at the moment - the most common canned response I have is "its a known problem with Microsoft". If you have 50,000 I dont know how you do it.
As for Flow, I am happy today it worked as expected, as it always has (without us making any changes to break or fix it) - but as for tomorrow - I cant tell my business it is a trusted, stable, Enterprise grade solution.
Flows failed again out of the blue - same error "The resource you are looking for has been removed, had its name changed, or is temporarily unavailable".
Still no response from Microsoft Support after four days despite about 10 requests for an update, so am flying blind and doing tests myself.
I dont believe the On New Email trigger is affected by the email count. I have written a program that allows me to send X number of emails with attachments Y in size and if I send a 100 emails with 1Kb files the trigger runs as expected.
However if I send 100 emails with 1Mb files it appears to crash. The crash is permanent, corrupting the Outlook Connector, and the flow will never resume unless the Connector is deleted, a new one created and the new one rebound to the Flow.
I have found reference to a 100Mb limit here : https://docs.microsoft.com/en-us/flow/limits-and-config - my testing suggests it could be well less that 100Mb for the On New Email trigger, may as low as 40Mb.
This is alll guess work as I am not getting any information or hints from the Flow error or Microsoft Support.
To tests I have replaced all my flows with a Schedule Trigger causing an Get all Emails action as shown below. I am hoping that processing the emails in batches of 10 will reduce the risk of hitting any unknown sum limit.
Again all guess work, and whilst I can accept limitations I would expect an enterprise solution such as Microsoft Flow would handle more than 40-50Mb of emails, expecially as it is bound to a mailbox that has a 150,000Mb capacity.
Or I would expect that if you encounter the error it doesnt crash the Flow permanently, or the error would give some helpful information, or Microsoft Support would be able to come back with something in 4 days.
I will continue updating the thread for the advantage of others who come across the issue, it is a warning that the more you use Flow it can encounter limitations quickly. I am not overally confident this is the fix, we have other Flows that are dissapearing as well.
Three of our Flows failed again over the weekend and again today.
Two Flows processed none of the emails, just returing the error "The resource you are looking for has been removed, had its name changed, or is temporarily unavailable" as they have on and off for the last four weeks and effectively every day for the last 10 days.
One Flow says it processed the emails, but none of them appeared in SharePoint.
I tried to log a support agreement via our Enterprise Agreement, and they advised this cannot be done, that they do not provide support for Microsoft Flow, rather we should try to find the "live chat" - but they were not sure what or where that was.
So there we go all - Microsoft Flow is not officially supported under your EA agreement.
Not exactly a techincal help, but have you thought about converting your flows into Azure Logic apps? Perhaps your flows will not be failing in there, or you would get better spport in case they do.