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
DDCJOEE
Resolver I

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. 

Sherif-Abolsaud
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.

notj
Post Prodigy

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.

kpartington-tr
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!

RachelRig
Advocate V

At the very least, it would help if the visited-link color would change, so after I dig into a Flow run, I could return to the run history list and identify which one I just looked at. It's really painful. 

KyleDoddemeade1
Frequent Visitor

It would be helpful to have the option to add a column which can be pre-populated from data from the flow run, such as a reference number of unique identifier so it's a bit easier to manage.

dtunforgettable
New Member

I also waste so many hours in a day trying to find a specific flow not only to see if it failed, but also to see if it has been approved, is still running or timed out.  

 

If anyone has any ideas I would reallyyyyyyyyyy  appreciate it. 

notj
Post Prodigy

@dtunforgettable you could check out this: Power Studio

 

They seem to have a lot of great features.

MarcBoes
Frequent Visitor

@dtunforgettable , another approach is the one I posted here: Flow history for SharePoint item - Power Platform Community (microsoft.com). Basically you create a (central in my case) SharePoint list where you write logging information and a link to the specific run of the flow. The steps are explained better and detailed better that I'd could: Microsoft Flow – Capture Hyperlinks and Detail about Running Flows (all credits to Chris Chance). His post ends with "As Flow matures, I suspect that Microsoft will enhance the Flow Portal to either include more detail or allow for modifications.  Until that happens I hope that this will help Flow owners and users make finding specific Flow instances easier."
Sigh, that was Sep 16th, 2019.

ONYXJas
Advocate IV

The first action step I always add after the trigger is a Compose showing the name of the item that fired the trigger, the user (this sometimes needs a [Get User Profile] to find the display name first) and the date, as a Checkpoint for debugging.

 

I also use Compose Checkpoints at key points in the logic, especially around conditional outcomes and loop constructs, just to track what's happening for debugging purposes.