cancel
Showing results for 
Search instead for 
Did you mean: 

Flow Run History - More Details!

Are there any plans to add more detail to the Flow run history list? I mostly work with SharePoint lists and it would be a HUGE help if we could see the name of the file or list item the flow ran on. Or just the list ID number? Person who triggered the flow? Anything? I really need some way to tell them apart.

Status: New
Comments
Helper II

I just came here to make this same suggestion! I have a flow that runs a LOT, and it would be incredibly helpful to be able to filter flow runs down to some kind of variable as mentioned in this idea. 

Frequent Visitor

That is a very valid request!

 

I am also using share point list, it is very difficult to point to a specific run to check anything I might need.

 

So, I suggest to have the option to dynamically choose a field from my flow to appear in that page so search and sorting will be available.

 

Or, give a new field code for each flow, and each run takes automatic serial number (flow code + serial) ex: Flow1_12000021133.

Also the option to find this value in the run outputs so I can pull it in any where (like share point list).

Then this serial to be showed in the run history page.

 

Or, any idea may help linking the outputs to the run, currently I am struggling and searching by run date time.

Responsive Resident

The current Flow History is just one step short of being completely useless. It is amazing how difficult it can be to find a specific failed run when you have 20 or so that failed all at once.

 

It would be amazing if you had a meta-action that was called "Set Flow Details Fields". In that action, you have a handful of custom fields that will show up in the Run History page. Let us set those fields to dynamic data from inside the Flow. Voila, MAGICALLY USEFUL.

Advocate I
It would be amazing if you had a meta-action that was called "Set Flow Details Fields". In that action, you have a handful of custom fields that will show up in the Run History page. Let us set those fields to dynamic data from inside the Flow. Voila, MAGICALLY USEFUL.

I agree 100%, this would be awesome!