It sounds like your "Unique test executions" graph in the Elementary report is only showing data for one day, even though you are running the same tests daily. This issue has been reported by other users and can be caused by a few different factors: 1. Data Collection Window (

days_back

): If the

days_back

variable is not set correctly, or if you changed it recently, Elementary may not be collecting or displaying historical data as expected. After changing

days_back

in your

dbt_project.yml

, you need to do a full refresh of the metrics by running:

dbt run --select data_monitoring_metrics --full-refresh

Then, rerun your Elementary tests and generate the report again. This ensures that the new time window is reflected in the report. Also, when generating the report, you can use the

--days-back

option to control how much history is shown in the UI (e.g.,

edr report --days-back 45

) [Anomaly Tests Troubleshooting Guide](https://docs.elementary-data.com/data-tests/anomaly-detection-tests/Anomaly-troubleshooting-guide). 2. Version-Related Bugs: There have been bugs in previous versions of Elementary where historical data was not displayed correctly in the dashboard, even though the underlying tables had the data. This was fixed in later versions, so make sure you are using the latest versions of both the Elementary dbt package and the CLI. After upgrading, users have reported that the graphs start to populate correctly with new runs, but it may take a few days for the history to fill in as new data is collected [Slack thread on missing historical data](https://slack.com/archives/C02CTC89LAX/p1740395350614099). 3. Data in Underlying Tables: Check if your

elementary_test_results

(or

test_run_results

) table actually contains data for the days you expect. If the table only has data for one day, the issue may be with how or when the tests are being executed or results are being written. If the table has historical data but the report does not show it, it's likely a reporting or configuration issue [Slack thread on test results](https://slack.com/archives/C02CTC89LAX/p1701813698582889). 4. Report Generation Timing: If you are running

edr report

or

edr send-report

before the test results are fully written to the warehouse, the report may not include the latest data. Ensure that your workflow allows enough time for test results to be committed before generating the report. Next Steps: - Verify your

days_back

settings and perform a full refresh if you changed them. - Ensure you are on the latest versions of Elementary. - Check the contents of your

elementary_test_results

table for historical data. - Make sure your report generation is happening after test results are available. If after these steps the issue persists, please provide more details about your setup, including your Elementary and dbt versions, and check if there are any errors in your logs. This will help further diagnose the problem.

Given your setup: 1. You are running

edr report --days-back 10

. 2. The

elementary_test_results

table contains test results for all days in that period. But the "Unique test executions" graph only shows data for one day. Based on the knowledge sources, here are the most likely causes and next steps: - Version-Related Bug: There have been recent issues where historical data was not displayed in the dashboard, even though the underlying tables had the data. This was confirmed as a bug and fixed in a newer CLI version. After upgrading, users reported that the graph started to populate correctly, but it may take a few days for the history to fill in as new runs are executed. Make sure you are using the latest version of the Elementary CLI and dbt package. If you recently upgraded, the graph should update as new test runs are added over the next few days. No need to rerun the Elementary tables unless instructed otherwise by support staff [Slack thread on missing historical data](https://slack.com/archives/C02CTC89LAX/p1740395350614099). - No Need to Rerun Models: Support staff confirmed that after upgrading, you do not need to rerun the Elementary tables; the graphs should update with subsequent runs. - Browser/Report Size Issues: In rare cases, very large reports (e.g., 1GB) can cause display issues in some browsers, but this is less likely if your report is much smaller and the issue is only with the "Unique test executions" graph [Slack thread on report display](https://slack.com/archives/C02CTC89LAX/p1705599897971779). What you should do: - Ensure you are on the latest Elementary CLI and dbt package versions. - Continue running your daily tests and generating reports; the graph should fill in as new data is collected. - If the issue persists after a few more days and you are on the latest version, it may be a new bug—consider reaching out to Elementary support with your version details and a sample report. If you have already upgraded and the problem continues, please provide your Elementary CLI and dbt package versions, as this will help further diagnose the issue.

Thank you for clarifying that you are running the report locally with

edr report --profile-target prod --days-back 10

and still see the "Unique test executions" graph with zeros except for one day, even though your

elementary_test_results

table has data for all days. Based on the knowledge sources, here are the most relevant points: - If your

elementary_test_results

table contains results for all days, but the report only shows data for one day, this issue has been observed before and was related to a bug in the Elementary CLI/dashboard. The recommended solution is to ensure you are using the latest versions of both the Elementary CLI and the dbt package, as this bug was fixed in a recent release. After upgrading, the graph should start to populate correctly as new test runs are executed, but historical data may only appear as new runs are added going forward. There is no need to rerun the Elementary tables for past data to appear; just continue running your tests and generating reports daily. If you are already on the latest version and the issue persists after a few days, it may be a new or unresolved bug, and you should reach out to support with your version details and a sample report for further investigation [Slack thread on missing historical data](https://slack.com/archives/C02CTC89LAX/p1740395350614099). - There is no indication in the knowledge sources that additional configuration or a different command is needed if the underlying tables have the correct data and you are using the correct

--days-back

parameter. If you have already confirmed you are on the latest versions and the problem continues after several days of new test runs, please contact Elementary support with your CLI and dbt package versions and a sample of your report for further troubleshooting. If you need more specific troubleshooting steps, please provide your Elementary CLI and dbt package versions.

Thank you for providing your version:

edr=0.18.1

. Based on the knowledge sources, there is no explicit mention of issues with the "Unique test executions" graph in version 0.18.1. However, similar issues in previous versions were caused by bugs that were fixed in later releases. The typical resolution was to upgrade to the latest version, after which the graphs would start populating correctly as new test runs were executed. There is no indication in the knowledge sources that additional steps are required if you are already on the latest version and your

elementary_test_results

table contains the correct data. Since you are on a recent version and still experiencing this issue, and your underlying data is present, the knowledge sources do not provide a specific solution for your scenario. The best next step, as suggested in similar cases, is to reach out to Elementary support with your version details and a sample report for further investigation, as this may be a new or unresolved bug in the current version [Slack thread on missing historical data](https://slack.com/archives/C02CTC89LAX/p1740395350614099). I'm sorry, but the knowledge sources do not contain enough information to provide a definitive solution for this issue in version 0.18.1.