Curious if others are seeing this bug: We have a boolean field that is empty by default. When it’s populated in the backend for the first time while the user is viewing a group containing the updated thing, the conditionals that are based on the now-populated boolean don’t trigger.
In debug mode’s inspector, the boolean is then listed as hidden due to privacy rules, but no privacy rules are restricting visibility of that boolean, nor are any privacy rules dependent on the boolean. Conditionals trigger after reloading the page, and the boolean is no longer listed as hidden in the debug mode inspector.
I was able to reproduce the issue across multiple data types, and it definitely wasn’t there before. Issue was resolved on new things after changing the default boolean value to “no” in the type settings, i.e. the field no longer being empty when the thing is created.