When you run

edr monitor

after a

dbt test

with a test failure, and you see only "Update skipped alerts" without a new Slack alert being sent, this is expected behavior in certain scenarios. Elementary is designed to avoid sending duplicate alerts for the same issue. Once an alert has been sent for a specific test failure, it is marked as "sent" in the alerts table. If you run

edr monitor

again without a new

dbt test

run (i.e., no new failures or changes), Elementary will recognize that there are no new alerts to send and will skip sending the same alert again. The "Update skipped alerts" message simply indicates that the process checked for alerts to skip (due to suppression intervals, duplication, or already-sent status), and found nothing new to send. This prevents alert fatigue and duplicate notifications. Here are some relevant points from the knowledge sources: - Alerts are skipped if they are not from the latest dbt invocation, or if they have already been sent and marked as such in the alerts table. If you run

dbt test

+

edr monitor

once, the alert will not be sent again unless there is a new failure or a new dbt run/test invocation. Suppression intervals can also prevent repeated alerts for the same issue within a set time window. [Source: Slack discussion on skipped alerts](https://slack.com/archives/C02CTC89LAX/p1696945250119199) - After each time

edr monitor

is executed and alerts are sent, those alerts are marked as "sent." If there are no new dbt runs or test failures before the next

edr monitor

execution, there are no new alerts to send, so nothing is sent and you see the "Update skipped alerts" log. [Source: Slack discussion on alert sending logic](https://slack.com/archives/C02CTC89LAX/p1684524581057829) If you want to trigger a new alert, you need to have a new test failure from a fresh

dbt test

run. Otherwise, Elementary will not resend the same alert to Slack.