A community member reported encountering an issue in ControlUp workflows involving “if/then” conditional statements. The problem occurred when previously accurate conditions appeared not to function correctly until the user cleared the input fields and retyped the values. This behavior suggested that breaking and re-establishing the connection between workflow nodes could affect how input boxes processed or retained their values. Specifically, conditions involving tag lists and byte size comparisons behaved inconsistently unless manually re-entered.
The user shared JSON data illustrating the conditions in question, which compared a calculated byte size against a threshold and checked whether a device tag list did not contain a specific tag (“dna_created”). Although the raw conditions were valid and logically sound, the workflow returned unexpected results until the inputs were cleared and retyped. Upon removing and manually reentering the lookup fields, the condition evaluations worked as intended.
Further investigation revealed that the issue could not be consistently reproduced and appeared to resolve itself after refreshing or reconnecting the nodes. A follow-up confirmed that the workflow conditions were working correctly in later tests, properly evaluating tag presence and logical operators to produce the expected false result when the tag list included “dna_created.” This suggests a transient glitch related to how ControlUp’s workflow editor handles input persistence or data-binding in condition nodes, particularly with dynamic references or lookups.
For users experiencing similar issues, a recommended workaround is to manually clear and retype values in the “if/then” condition inputs to force a refresh of the connection state. If the issue persists, recreating or reconnecting the nodes may help restore proper evaluation. Keeping ControlUp updated to the latest version may also mitigate such transient inconsistencies. For more details on workflow conditions and node behavior, refer to ControlUp’s official documentation on workflows and condition nodes at https://docs.controlup.com/solutions/workflows.
Read the entire ‘Resolving Condition Input Issues in ControlUp Workflows: Retyping and Node Reconnection Best Practices’ thread below:
I see new node options in workflows this morning but wanted to call out that yesterday I spent hours going in circles with if then statements. come to find out my statements were accurate but only after clearing the fields and retyping back into the if\then. almost like breaking the connection between nodes and reconnecting somehow affects the input boxes? any insight to this?
Hi Robert,
Thank you for posting!
Are you able to reproduce this behavior and record it?
Tagging and for their awareness
emailing this over versus chat
“`{
“input”: {
“conditions”: {
“raw”: [
{
“if”: “{{calc_byte_gb.result}}”,
“is”: “{{Greater Than}}”,
“logic”: “{{AND}}”,
“to”: “10”
},
{
“if”: “{{list_device[i].tags}}”,
“is”: “{{Does Not Contain}}”,
“logic”: “{{AND}}”,
“to”: “dna_created”
}
],
“actual”: [
{
“logic”: “AND”,
“if”: 16.610291712,
“is”: “Greater Than”,
“to”: “10”
},
{
“logic”: “AND”,
“if”: [
“9325f3”,
“strat”,
“ring_4”,
“shm-strat-alt”,
“lowdisk”,
“dna_created”,
“25h2”
],
“is”: “Does Not Contain”,
“to”: “dna_created”
}
]
}
}
}
{
“status”: “completed”,
“result”: false
}“`
if i delete out the lookups and retype, no issue
does it still happen today?
just to keep you on the loop.
• We met today, and could not repro. All working well today
• Node details above are working as expected. Condition: Tags do not contain dna_created. Result: false, because the tag list in actual includes dna_created
Thanks again for this – late night had me “contain”ing too much
Continue reading and comment on the thread ‘Resolving Condition Input Issues in ControlUp Workflows: Retyping and Node Reconnection Best Practices’. Not a member? Join Here!
Categories: All Archives, ControlUp Workflows
