I am working on a rather extensive flow. It doesn't pertain to my question to talk about what it does. Quite simply, I am baffled at the way the 'is null' operator is working in a decision element. At the very start of my flow, I am checking if two of the triggering record's fields are null. If they are, I want the record to take a defined path. Otherwise, the record should take the default path. Here is a snap shot of how I have this set up:
However, when I go to run the flow debugger, I get some odd behavior. Since the record I am running the flow with the debugger does not haver either the 'individual email' or 'individual linked in url' fields set, I would expect the debugger to take my 'No unique person identifiers' path. However, it is taking my default path. Here is a picture of the debugger message and flow path (please keep in mind that BOTH the relevant field are not set, so should be null):
Since both of the relevant fields are not set yet, I would expect the record to take my defined path, rather than the default outcome. Why is this happening? Do I have a misunderstanding of what 'Is Null' is for and how it behaves? Also, in the debug log, what does 'Record(null) is null null' mean? Please help!!!