What We Fixed
- A condition using Was Less Than or Was More Than on a date field now works. Previously any automation with one of these conditions stopped at that step: the condition was treated as unmet, the run was marked skipped, and nothing after the condition ever ran — with no error shown.
- This affected every date and datetime field, including Last Call Made, Last Text Sent, Last Text Received, Last Email Sent, Last Email Received, Last Newsletter Sent, Created At, Last Activity Date, and custom date fields. “Hasn’t been contacted in N days” automations are the common case and were fully broken.
- The same fix applies to Lead Flow rules, which used these conditions through the same evaluator.
What to Expect
- Existing automations start working without being edited. An automation that appeared to do nothing will now continue past the condition and run its remaining steps the next time it is triggered. If you built a workaround for this, it is worth reviewing before the automation runs again.
- Contacts that repeatedly re-entered and re-skipped an automation under a “never” re-enrollment policy will now be evaluated properly.
- Coming Up in Less Than and Further Than — the two future-facing date operators — are not part of this fix and still do not evaluate. They behave exactly as before.