When I enter to microsoft flow and click on myflows i get the following error:
Encountered internal server error from Azure Resource Manager. The tracking Id is
Microsoft announced an issue: Error: Beginning at 2019-10-30 10:26 UTC users worldwide began experiencing problems listing, viewing, or saving flows and listing or switching environments.
Thus we have to wait for MS to solve the issue.
it wasn't just that I didn't have access to my flows. A business integration triggered by a webhook was offline for 2 hours! This means that the flow did not trigger or run for over two hours!
Please let me know if it was a bigger problem than just a "UI problem"!
Hey guys I was not happy either but we ve been down for 2h in the past year. The SLA is 99.99% of availability I believe that with 2h of downtime per year MS still meet this SLA.
Page 66 says <99.9% uptime per month with 25% credits.
For 99% is 50% credit.
2 hours per month (31 days x 24 hours) is about 0.997 %. Downtime per year is not mentioned.
What is the current situation on your side, this is a known issue, please check the message posted by MS Flow Support:
Users in some areas may not be able to use Flow normally, and this issue is being fixed.
There are some users who reflect that MS Flow is working properly, please try again.
If the problem persists, please let us know.
Check out the new Process Advisor community forum board!
Check out new user group experience and if you are a leader please create your group
On-demand access to all the great content presented by the product teams and community members! #MSBizAppsSummit #CommunityRocks
Check out how to claim yours today!