You’re offline. This is a read only version of the page.
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?
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.
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.
#1
Michael E. Gernaey
497
Super User 2025 Season 2
#2
David_MA
436
Super User 2025 Season 2
#3
Riyaz_riz11
244
Super User 2025 Season 2
Share
Report
All responses (
Answers (
