Unanswered

How can I see the actual inputs to the condition (or other) actions in the flow run history?

(4) Share

Report

Posted on by AaronO

150

When building flows and troubleshooting, one of the most basic requirements to succeed is to be able to see the information which is being passed from one action to the next, especially in the case of conditions. As far as I can tell, there is no way to see the information which caused a condition to pass or fail. When working with multiple conditions in a condition action, this makes it nearly impossible to troubleshoot, and we're left with blind trial and error as the only method to understand how the flow is behaving.

Show raw inputs is useless. For example, the "raw input" displayed for the condition I need to understand is just the result value of false. And a variable I need to know the value of only shows the type "string" and not the value in the raw inputs. I could not conceive a more frustrating way for a feature to fail.

Am I missing something, or is it really this bad?

Categories:

Building flows

I have the same question (0)

All responses (2)

Answers (1)

Verified answer

Mitanshu 1,650 Moderator on at

Like (2)

Report

Just before the Condition, you can add a Compose action and list down all your variables that you want to see for the purpose of troubleshooting.

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly. If this post helped you in other ways, please click the Thumbs Up button.

Was this reply helpful? Yes No
AaronO 150 on at

Like (14)

Report

Thanks! I'll accept this as the solution since it does allow me to see the information in-line. But this type of functionality really should be included in the flow run history. If not in the production history, at least include it in the test runs.

Was this reply helpful? Yes No