Incorrect triggering of automation, using Anniversary trigger

Does anyone else us Anniversary to trigger automations?
In my case I am using Anniversary to trigger emails and sms in the run up to client’s EVENT DATE, which has been added as an Attribute, and this is used to trigger the automations.

I have created ‹ 24 months to go › automations down to ‹ 5 months to go ›, so almost 19 automations but contacts are added to automations randomly. One client is in 2 automations and receiving communications saying « 2 years to go » and « Not long now » emails at the same time.

Pretty critical I get this fixed! Any help appreciated

Hi Neil, I’d use a Contact filter as an additional safeguard, but it probably won’t solve the underlying issue on its own.

In each workflow, open the Anniversary trigger, select Contact filters > Add filter, and set:

  • Status is not Booked
  • EVENT_DATE is not empty
  • Use AND between the conditions

However, the Anniversary trigger ignores the year and evaluates the recurring day and month. It is therefore better suited to birthdays or annual anniversaries than to a one-off 24-month countdown. Contacts can also be active in multiple automations when more than one trigger matches.

For this use case, I’d recommend using a full-date/date-based trigger, if available in your editor, or one workflow with the earliest reminder followed by delay steps for each subsequent message. Add an If/Else status check before each send, so contacts who become Booked stop receiving communications. Keep contact re-entry disabled if this is a one-off event.

If contacts still enter the wrong workflows despite these filters, send Brevo Support the affected workflow IDs and several examples from the last five days so they can investigate the automation logs.

Useful guides:

I hope this helps!