Flow filtering based on a custom property that may or may not exist

Hi @Chops,
Welcome to the community)

If a profile does not have the subscription_status custom property set, then the flow filter condition you've set will evaluate to false for that profile. In other words, the profile will not meet the condition that subscription_status does not equal "active", but it also won't meet the opposite condition that subscription_status does equal "active".

When a flow filter evaluates to false for a profile, it does not prevent that profile from receiving the message or proceeding through the flow. Instead, the flow will continue as if the filter condition was not present, and the message will be sent to the profile as scheduled.

If you want to ensure that profiles without the subscription_status custom property set do not receive the message, you can modify the flow filter to include an additional condition that checks whether the property exists. You can do this by using the does not exist operator in combination with the subscription_status custom property. Here's an example:

Subscription_status does not equal active AND Subscription_status does not exist

With this modification, the flow filter will evaluate to false for profiles that either have a subscription_status property with a value of "active" or do not have the subscription_status property set at all. This will effectively exclude these profiles from receiving the message.