Bug Fix

Relative Date Conditions in Automations Now Evaluate Correctly

What We Fixed

  • An automation Condition such as Created At — Was Less Than — 7 Years now passes for contacts that meet it. Previously a Was Less Than / Was More Than condition built in the automation editor was treated as unmet for every contact, whatever number and unit it used, so the run was skipped at that step.
  • When a Condition like this is the first step after a trigger, it is checked before the contact is enrolled. Those contacts were being turned away silently, which is why some automations showed no triggered runs at all.
  • The automation’s run history now shows these conditions in plain language, for example created_at was less than "7 years", instead of "[object Object]".

What to Expect

  • Existing automations start working without being edited. Contacts that meet the condition will continue past it the next time the automation is triggered. Contacts that were turned away earlier are not re-run automatically.