Automations built with a Condition node set to Phone Is Good or Email Is Good were evaluating as Not Met for every contact — even when the contact’s phone showed Valid and Not on DNC List and had an email on record. As a result, every step after the condition was silently skipped, while automations without a Condition node (e.g., snail mail steps) ran normally.
What’s Fixed
- Phone Is Good now matches when the contact has at least one phone whose validation came back Valid. Phone Is Bad matches when the contact has phones but none are valid.
- Email Is Good / Email Is Bad now correctly read the contact’s email quality grade, the same way the matching Smart List filter does.
- Automation and Smart List logic for these conditions now stay in sync — what passes the filter in a Smart List will also pass the same automation condition.
Heads-Up
Automations that have been silently no-op-ing because of this bug will start running again on the next evaluation. If you have Phone Is Good or Email Is Good Condition nodes on high-volume tag triggers, expect a one-time catch-up of conditioned steps (texts, calls, emails) for contacts that already match.
Migration
No action required. Existing automations don’t need to be re-saved — the fix applies the next time each automation runs.