cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Share your ideas and vote for future features

Suggest an idea
calvares

Export flow history - more than 100 runs

Submitted on ‎01-28-2019 04:06 AM Submitted by Continued Contributor on ‎01-28-2019 04:06 AM
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
Status: New
See more ideas labeled with:
14 Comments (14 New)
sergeluca

Flow history

Submitted on ‎06-01-2017 11:22 PM Submitted by on ‎06-01-2017 11:22 PM
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
Status: Under Review

Hello, the recommendation would be to not use Flow history as a permament audit log. For example, the Approvals history is kept forever and you can use that for Approvals scenarios. For other scenarios, you can log to Cosmos DB or Blob storage. 

See more ideas labeled with:
  • Flow history
12 Comments (12 New)

Easier troubleshooting - show custom error-code from terminate action in run history

Submitted on ‎01-18-2019 12:17 AM Submitted by Anonymous on ‎01-18-2019 12:17 AM
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
Status: New
2 Comments (2 New)
bmi-at-k2

Flow History Improvements

Submitted on ‎02-11-2019 04:22 AM Submitted by on ‎02-11-2019 04:22 AM
Allow us to give a name for each flow occurrence.  This name should be visible in the Flow history. It would be nice if the colour coding for "Cancelled" and "Failed" flows is different. Further, please make sure when a flow is Resubmitted this is somehow portrayed in the Flow History, too   ... View more
Status: New
See more ideas labeled with:
  • Flow history
2 Comments (2 New)
Labels

Helpful resources