Submitted on01-16-201907:08 AMSubmitted byAnonymouson01-16-201907:08 AM
The email sent by Flow, "[#] of your flows have failed," currently does not differentiate between failed flows and cancelled flows. It would be helpful to exclude cancelled flows when generating this email as usually there is no issue and nothing that needs attention as cancelled flows are expected behavior (when the result of a condition) or have already been tended to as they were cancelled by an admin.
... View more
Submitted on12-04-201809:39 AMSubmitted byTanneron12-04-201809:39 AM
Currently, Microsoft Flow will disable any flows that have been in a problem state for 30 days. This is entirely too long for any real business application, and should be much shorter. Ideally, users could pick how many days (e.g. 1 thru 90, or 0 to disable the feature) of continuously failed Flows/a continuous error state should last before the Flow is automatically disabled, but at the very least we should be able to choose between a couple presets (e.g. 1 day of failures, 1 week, 4 weeks). Additionally, Microsoft Flow should include in its notification email *what the error was*. E.g. "One of the connections used in this Flow does not have adequate permissions" or "The Flow failed due to a conflict with your company's DLP policies", etc.
... View more