or vice versa, the UI appears to be converting them under the hood to strings (
, as the case may be). This causes conditional logic that checks for “truthiness” in my flow to behave incorrectly (i.e. conditionals expecting a
always evaluate as
since non-empty Python strings always evaluate as
). I verified this by toggling the values in Inputs UI and switching to the JSON configuration view of the data. I can get the Flow to run correctly by switching to the JSON configuration and correcting the issue, but figured that perhaps I’m missing something basic about the UI. Anyone have advice?
in the UI, the value is converted to a string as shown in the JSON view below
values as proper booleans and my flow works correctly (see image below). So perhaps this is just a quirk related to toggling to JSON configuration mode? Anyhow, sorry to bug you all on the weekend with it. Let me know next week if you have any follow-ups to help reproduce the issue