Elementary Community

Hello, we have an issue where running `dbt run` triggers sending past day's `source freshness` alerts, even if they have already been sent. I checked the alert_source_freshness table and noticed that the same alert was properly marked as 'sent' in the previous source freshness run. After `dbt run` finished running, the past day's `source freshness` alerts were updated to 'pending,' and then, they were updated as 'sent' again with the most recent sent_at timestamp.

Screenshot 2023-10-31 at 9.18.00 AM.png

Hello <@U02BVBCC0CC>, I noticed some questions after mine have been picked up. Could you also have someone take a look at mine? This repeating alerting issue is affecting our work. Thanks:pray:

Hello <@U05U80GV2SY> , may I  get some support on this?:thankyou:

Hey <@U05EY8B2Q2Y>!
Sorry for the delayed response
Does this happen on every run? Can you share your dbt, edr cli and elementary package versions?
If this still happens it would also help if you could share your `dbt.log`