To configure all Elementary tests to have a severity of "warn" (so they warn rather than fail), you can try adding the following block to your `dbt_project.yml`:

yaml tests:   elementary:     +severity: warn

This approach is based on dbt's project-level test configuration, which should apply the

warn

severity to all tests under the

elementary

namespace. However, please note that there are multiple reports from the community that this configuration does not always work as expected for all Elementary test types or versions. Some users have found that even with this configuration, certain tests (like

elementary.volume_anomalies

) may still error out instead of warning, depending on the Elementary and dbt versions in use. There is no confirmed universal solution in the knowledge sources, and some users have resorted to setting the severity per test as a workaround [see discussion here](https://slack.com/archives/C02CTC89LAX/p1711559815403719) and [here](https://slack.com/archives/C02CTC89LAX/p1688028623624369). If the project-level config does not work for your setup, you can explicitly set the severity in each test like this:

yaml - elementary.volume_anomalies:     config:       severity: warn

This per-test configuration is confirmed to work [as described here](https://slack.com/archives/C02CTC89LAX/p1709141168413439). In summary: - Try the project-level config first. - If it doesn't work for your version, set

severity: warn

in each Elementary test's config block. Let me know if you need more specific guidance for your setup!