We have program entry queries in place to add records to look for notification date = today (see full criteria below). There are times where the harvest fails and "bad" records are put into programs. Since we have a nightly ETL process that updates the Main Database, so if a bad record makes it into a program and the date doesn't = today, then the user receives a notification with text that says "Not Applicable" (this is the text in the database when a user shouldn't get a notification). I'd like to suggest a product enhancement of adding logic to block sends where the fields are null or say "Not Applicable" so bad records don't reach the end user.