A debug tip for complex conditions in Power Automate #FlowNinjaHack 126
/This is #FlowNinjaHack 126
Sometimes, we have complex Condition blocks in Power Automate.
And when we run the flow, it just shows “false”, which is a bit hard to debug.
One way I’ve started doing, is to write a Compose debug statement that shows the output of each component of my condition.
I show the Code View here as well so you get the idea.
To convert from the Condition block to these expressions can be a bit tricky, since you can’t use Code View easily for Condition. So here’s a second hack.
Paste this to a text editor, something that understands JSON. You’ll get this part.
"type": "If",
"expression": {
"and": [
{
"not": {
"equals": [
"@outputs('Get_item_-_Bulletins_list')?['body/Status/Value']",
"Draft"
]
}
},
{
"not": {
"contains": [
"@body('Select_page_filename')",
"@variables('varTitle')"
]
}
},
{
"contains": [
"@body('Select_page_filename')",
"@outputs('Compose_-_Old_Title')"
]
}
]
}
Now this is still not the right format, but you can then go from this to:
not(contains(body('Select_page_filename'), outputs('Compose_-_Old_Title'))
With a lot less pain.
This is the debug message you’ll see when you run now.
