If your Elementary schema test results are not synchronizing and updating in the Edr HTML dashboard, there are several common causes and troubleshooting steps based on the knowledge sources: 1. Profile Configuration Mismatch The most frequent issue is a misconfiguration between the dbt project profile and the

elementary

profile used by the Edr CLI. The

elementary

profile in your

profiles.yml

must point to the same database and schema where the Elementary dbt package writes its results (typically

<your_schema>_elementary

). If these do not match, the report will not display the latest test results, even if the tables are populated in your warehouse. Double-check that the

elementary

profile is correctly set up and used by the Edr CLI when generating the report. You can use the

edr debug

command to validate the connection and configuration [see example](https://slack.com/archives/C02CTC89LAX/p1681158042126419), [another example](https://slack.com/archives/C02CTC89LAX/p1659002103951729). 2. Static Nature of the Report The Edr HTML dashboard is a static file. It does not update automatically; you must re-run

edr report

after running your dbt tests to generate a new report that includes the latest results. If you want this to happen automatically, you need to automate the process (e.g., in your CI/CD pipeline) or consider using Elementary Cloud, which supports automatic synchronization [details here](https://slack.com/archives/C02CTC89LAX/p1715325264893609). 3. Version Compatibility Incompatible versions between the Edr CLI and the Elementary dbt package can cause the report to not display results. Ensure that your

edr

version and the Elementary dbt package version are compatible. If you see warnings about version mismatches in your logs, update your packages accordingly [see example](https://slack.com/archives/C02CTC89LAX/p1711981966108649). 4. Test Results Not Written If the test results are not being written to the correct schema/table, check your dbt logs and ensure that the Elementary dbt package is installed and enabled. Also, verify that no flags are set to disable Elementary’s on-run-end hooks (such as

disable_dbt_artifacts_autoupload

) [see example](https://slack.com/archives/C02CTC89LAX/p1708786310140179). 5. Schema or Table Issues Sometimes, multiple or incorrect schemas (e.g.,

elementary

,

elementary_elementary

, etc.) are created due to misconfiguration. Ensure only one schema is being used and referenced in both your dbt and Edr configurations [see example](https://slack.com/archives/C02CTC89LAX/p1682598527032289). Next Steps: - Double-check your

profiles.yml

for the correct

elementary

profile. - Ensure you are running

dbt test

with your main project profile, then

edr report

with the correct

elementary

profile. - Re-run

edr report

after each test run to update the dashboard. - Check for version compatibility and update if needed. - Review your logs (

edr.log

and

dbt.log

) for errors or warnings. If you follow these steps and still do not see results, please provide your log files and configuration details for further troubleshooting.