Skip to main content

Alert Builder: Frequency-Based Conditions No Longer Available as WHEN Triggers

Learn about migrating frequency based triggers from WHEN to IF conditions

Problem

In the legacy alert builder, frequency-based conditions (e.g. number of events > X, number of users > X) could be added directly as WHEN triggers alongside "a new issue is created." The new alert builder no longer supports these as WHEN triggers — they are now IF filters only.


​Resolution:

To replicate ANY-style logic across multiple frequency-based conditions, create multiple IF/THEN blocks within a single alert rule — one per condition.
​
For example, to fire when a new issue is created or event volume spikes or user count spikes, create three separate IF blocks under a single alert only WHEN: an issue event is captured, the relevant IF filter (e.g. number of events > 3 in 5 minutes), plus any shared attribute filters, and the same THEN action. The alert fires when any block's conditions are met.
​
If you manage alerts via Terraform some of the legacy triggers are still supported using legacy_trigger_conditions but not the frequency based onces.
​
For now the API does support frequency based trigger conditions but we intend to deprecate this eventually.

Did this answer your question?