Return Output even for Successful Flows

(2) Share

Report

Posted on by NickTT

248

So if you a child flow, you can pass inputs and outputs from that child flow. This gives you the option to show additional columns in the run history which is awesome. However I have I standard workflow that looks for updates to a database if some data changes. I collect the status "Updated", "Added", "Errored" and "Duplicate" for each record this workflow processes and then emails me the status of the run (IE: Updated: 100, Added: 2, Errored: 0, Duplicate: 10). Is there a way to show the status in the run History without calling a child flow? Right now my only thought is create a Child flow called "Status Outputs" or something and just have a the inputs and then an respond action. It doesn't really do anything but the main flow would then give me the options to quickly browse through the run history without having to go back to my email and try to correlate the email date with the run history.

Categories:

Building flows

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Suggested answer

David_MA 14,554 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

I am not sure how to do what you're asking, but if nobody has a solution, why don't you create an Excel spreadsheet with those columns. Then when the flow runs, just add a row to the spreadsheet with the values. That way you can also easily see a complete history of the runs and do analytics on the data. Instead of the run history, which is only saved for 28 days, you have a complete history in the spreadsheet.

Was this reply helpful? Yes No
abc 123 789 Moderator on at

Like (0)

Report
Copy link

Link copied!

The Run History only shows input parameters, not output. However, the email can contain the Database Item/Row ID, which I would assume is part of the input parameters of the automatically-triggered Flow. Add it to the Run History list, and use Ctrl-F to help locate it. (Since the interns can't be bothered to allow us to sort nor search the list.)

That said, anytime you execute the Run a Child Flow action, a RunID is created. (It's in the upper right corner of the action, when viewing the Parent run instance.) I copy that ID, and then open up any run instance of the child, and then swap out the copied RunID. Then I can review what happened in that child run. Look for /runs/ in the browser URL.

I love the idea of having the child call a child, and pass the status value as an input parameter, but getting back to the parent or grandparent would probably require the timestamp matching.

Was this reply helpful? Yes No