Hi #C02CTC89LAX, we started to receive multiple alerts for the same test, model or source freshness failure. Looking at some previous comments, I am pretty sure it happens because we have multiple nodes in our orchestrator that can sometimes run in parallel with

edr monitor

command, just because we can call multiple jobs that can run at same time and we are running them with template that will build them first and call the monitor after. Can we overcome this somehow? @Milos Blagojevic Thanks

hi @Luka, sorry for the late response 😅 the edr command should not be run in parallel, you should find a way to stop that in your orchestrator (maybe limit the amount of parallel runs if it is possible, or maybe change it so only the main job runs the edr command, it depends on the way you set things up)

Thanks @Ofek Weiss , we just removed edr command from template that we are calling on every project build and now we are running edr command on its own every 10 min. Maybe we will find better solution, but this works for now. It is hard to do main job idea, because we just democratized dbt build with other data teams and it’s just hard to predict if 10 different projects can be triggered at the same run. We will look for better ideas but we are ok with this one. Thanks 😃

Amazing! glad to here you found a solution drop stoked