I’m trying to use

volume_anomalies

and

freshness_anomalies

as gating tests, where a failure in either of these tests in an upstream model causes all downstream models to

SKIP

. While this is the default functionality for other DBT tests like

not_null

, I am not seeing the downstream `SKIP`s in response to failures in these elementary tests. After investigating my project’s

graph_summary.json

(docs), I see that the DAG after test edges have been added shows that my anomaly tests are not inheriting the downstream models as child nodes (i.e., they do not appear under the

succ

key). However, tests like

not_null

do appear with the downstream model as an explicit child node. How can I configure my elementary anomaly tests so that test failures cause `SKIP`*s in downstream models?* (Builds on prior thread)

I am facing the same issue. I would like to have this behavior as well. I would like to have the option to make test SKIP downstream models. #C02CTC89LAX

Hi @Francisco and @joshuah.kapilivsky! let me check this with the team

Hi @Or Avidov. Did you have an opportunity to check with the team on configuring anomaly test failures to cause downstream SKIPs? Is there a GitHub Issue or similar I can follow? Thanks again, we love elementary and I’m recommending it to all the teams throughout our org!