Flow storage is 30 days. Worklow history in SharePoint is 60 days and everybody complains about this (much much too short for compliance reasons like GPDR). We must be able to audit our Flow years after the worklow ends. Could be a paid option, or a way to export the flows history (Powershell) ... View more

Could we get rid of the 100 run limit on the flow history export? Since the online flow history is not easily searchable currently, we need to be able to download all records that are available. Secondly, since the flow history is only available for 30 days, we need to regularly download the history of flows. If we don't even get the full 30 days, then this is not useful to us. ... View more

Hi fellow Flow enthusiasts,   TL;DR: Make error-codes from the Terminate-action visible in the run history of Flow.   Please UPVOTE this idea if you find it useful und would like to see this in the future. Additional improvements can be stated in the comment section   We all have been there. You have X amount of flow runs, all succeeded but only 1 of them is the Flow which you are searching for. With the "Terminate"-action we finally can manually let the unimportant Flows fail or cancel instead of marking the exceptions as succeded. This is already a step in the right direction. Also they give u the opportunity to set custom error-codes and messages if we let the flow fail manually.              If this error-code (and possibly even the message) would be dislayed and it could be filtered upon that property this would make troubleshooting flows way easier. There could possibly also a code be used in the cancelled runs.   ... View more