It’s likely due to two changes: 1) Sampled failed rows are only stored if sampling is enabled. Ensure you haven’t disabled it and that samples are being written: - Set in dbt_project.yml:

vars:   elementary:     test_sample_row_count: 5   # or higher

Elementary stores these samples in the warehouse (test_result_rows / test_results_samples) and not raw data by default. [[Security & privacy](https://docs.elementary-data.com/cloud/general/security-and-privacy#what-information-does-elementary-collect%3F); [Athena thread](https://slack.com/archives/C02CTC89LAX/p1741861180336069)] 2) With dbt 1.8+, you must allow Elementary to override test materializations so samples are captured. Add:

flags:   require_explicit_package_overrides_for_builtin_materializations: false

This fixes empty test_result_rows on newer dbt versions. [[dbt 1.8 flag](https://slack.com/archives/C02CTC89LAX/p1734111312018389)] Notes: - You can increase sample size via test_sample_row_count; by default it’s small (e.g., 5). [[Sample size var](https://slack.com/archives/C02CTC89LAX/p1682955847416029); [store samples table](https://slack.com/archives/C02CTC89LAX/p1696900519445739)] - Only samples are stored, not all failed rows. [[Subset stored](https://slack.com/archives/C02CTC89LAX/p1709061533176029)] - If you customized tests or rely on temp tables, copying the “result query” may not work for some anomaly tests due to temp tables; this is a known issue in older versions. [[Invalid temp table query](https://github.com/elementary-data/elementary/issues/1483)] After applying the flags/vars, rerun tests and edr report; the “Test results” section should show samples again pulled from test_result_rows. [[Sample rows feature](https://slack.com/archives/C02CTC89LAX/p1704319265407929)]

If test_result_rows has data but the report’s “Test results” section is empty, it’s usually a profile/config or dbt 1.8 materialization issue. Try: 1) Verify the Elementary CLI profile - profiles.yml must include a top-level profile named elementary, pointing to the same warehouse/catalog/schema where your Elementary models live (typically <your_schema>_elementary). The file should be under HOME_DIR/.dbt, or pass --profiles-dir to edr. [[Troubleshooting OSS](https://docs.elementary-data.com/oss/general/troubleshooting); [Empty report fix](https://slack.com/archives/C02CTC89LAX/p1660748994945629); [Profile pair example](https://slack.com/archives/C02CTC89LAX/p1736248012807089); [BigQuery case](https://slack.com/archives/C02CTC89LAX/p1659002103951729)] 2) Ensure Elementary package models exist and are populated - Run dbt run --select elementary, then dbt test. Confirm elementary_test_results has data (you already have test_result_rows). If tables were materialized as views or overridden, recreate them with: dbt run --select elementary --full-refresh. [[Troubleshooting OSS](https://docs.elementary-data.com/oss/general/troubleshooting)] 3) For dbt 1.8+ - Add to dbt_project.yml to allow Elementary to override test materializations so result rows are captured and read properly: flags: require_explicit_package_overrides_for_builtin_materializations: false Then rerun dbt test and edr report. [[Athena thread](https://slack.com/archives/C02CTC89LAX/p1734542603784779); [Result rows empty fix](https://slack.com/archives/C02CTC89LAX/p1736200862741069); [Another report](https://slack.com/archives/C02CTC89LAX/p1734111312018389)] 4) Re-run edr and check logs - Run: edr report (or edr report -u true to refresh internal packages) and inspect edr.log in your working directory; also check the inner dbt log at <python site-packages>/monitor/dbt_project/logs/dbt.log for query/profile errors. [[Troubleshooting OSS](https://docs.elementary-data.com/oss/general/troubleshooting); [Log paths help](https://slack.com/archives/C02CTC89LAX/p1659547684760609); [Another empty report flow](https://slack.com/archives/C02CTC89LAX/p1657572412263959)] 5) Confirm sample count var - Vars example (default is small, but presence isn’t required for visibility): vars: test_sample_row_count: 5 This controls how many failed rows are stored, not whether the section appears; the section missing usually points back to profile/connection/materialization. [[OSS FAQ](https://docs.elementary-data.com/oss/general/faq)] If it’s still empty after these steps, please share edr.log and the elementary profile block so we can pinpoint the issue. [[Troubleshooting OSS](https://docs.elementary-data.com/oss/general/troubleshooting)]