Workflow History list in FLow

[goyals]

So one of the things about designing worklows using flows is that you don't get the detailed history of workflow like in it's predecessor SharePoint designer workflows we did using the workflow histroy list. I know there's the workflow run history and you can see the workflow steps but it's still very half baked and isn't customizable at all. 

Is there any way to replicate the workflow history using Flows?

Ideas & suggestions?

[v-yamao-msft]

Hi @goyals ,

Do you want to replicate the Run history of flows using Microsoft Flow?

I am afraid that it is currently not possible to replicate the run histories. If you need this feature, please just feel free post it on Flow Ideas Forum:

https://powerusers.microsoft.com/t5/Flow-Ideas/idb-p/FlowIdeas

Best regards,

Mabel

[goyals]

Thanks, I just think that the very verbose logging in the SharePoint Workflows was much more detail oriented and helpful for auditing purposes or just to look at what all happened in the workflow if somebody had to look back. There was much more control to developers to log to history list be it for testing/ additional steps logging for business purposes. 

I wanted to learn if w can do something similar in Flow which to my knowledge so far is not a possibility

[MarkStokes]

Hi Goyals,

I’m afraid that you aren’t comparing apples with apples. Microsoft Flow is not a SharePoint technology. At all.

I come from a similar background and I see Flow as a replacement for my SP Designer workflows and it is. But it’s also so much more.

But, that also means that it isn’t as tightly coupled to SP as SPD workflows were. Some people use Flow only with DCRM, or salesforce, or Azure, or SQL, so a “Write to Workflows History List” Action just wouldn’t make sense. It would for SharePoint on to people who may not be thinking about SharePoint.

However. I do achieve something similar. But I roll my own.

At some stages of my Flows I write entries our to a Workflow History list that I created myself. I just write out a related list item ID and a message. That way, I have my workflow history list just as I did before. But... I could write that to SP, or Excel, or SQL or Azure table storage or anywhere else I wanted.

- Mark