Thank you for your detailed description and for sharing your versions and steps. Based on the knowledge sources, here are some key points and limitations regarding your use case: ### 1. Visualizing dbt Source Freshness Results in Elementary Currently, Elementary OSS does not support visualizing dbt source freshness results in the Elementary dashboard. While you can upload source freshness results using

edr run-operation upload-source-freshness

, these results are not displayed in the dashboard. Instead, Elementary supports sending dbt source freshness results as Slack alerts, but not as part of the dashboard UI. This is a known limitation and there is an open issue to add this feature in the future. For now, only Elementary's own freshness tests (like

freshness_anomalies

and

event_freshness_anomalies

) are shown in the dashboard, not the native dbt source freshness results you upload [dbt source freshness dashboard support](https://slack.com/archives/C02CTC89LAX/p1684734955417799) [dbt source freshness dashboard support 2](https://slack.com/archives/C02CTC89LAX/p1677715870599249). ### 2. Error When Running

edr report

The error message you’re seeing (“Failed to run dbt command. Please reach out to our community for help with this issue.”) is a generic error that can have several causes. Based on similar issues in the knowledge sources, here are some common troubleshooting steps: - Check your

profiles.yml

and dbt configuration: Make sure the

elementary

profile is correctly defined, the target is set, and the schema/database matches where your Elementary tables are created [profiles.yml troubleshooting](https://slack.com/archives/C02CTC89LAX/p1680035534817339) [profiles.yml troubleshooting 2](https://slack.com/archives/C02CTC89LAX/p1698126672939689). - Version compatibility: Ensure that your

elementary

dbt package version matches your CLI version. Mismatched versions can cause errors. After updating, always run

dbt deps

and

dbt run --select elementary

 [version compatibility](https://slack.com/archives/C02CTC89LAX/p1718699125596869). - Check logs: Look in the

edr_target

directory for

edr.log

and

dbt.log

files. These can provide more specific error details [log files](https://slack.com/archives/C02CTC89LAX/p1695913966874839). - Database access: Make sure the CLI has access to the correct schema/database and that the tables exist where expected [elementary schema troubleshooting](https://slack.com/archives/C02CTC89LAX/p1688546626227049). ### 3. Summary - You cannot currently visualize dbt source freshness results in the Elementary dashboard. - The error you’re seeing is likely related to configuration or version mismatch. Double-check your

profiles.yml

, schema/database settings, and ensure your package versions are aligned. - Check your logs for more details and consider sharing them with the community for more targeted help. If you need to visualize source freshness, you may need to use Slack alerts or wait for future updates to the dashboard feature. If you can share the specific error trace from your

edr.log

or

dbt.log

, I can help you further pinpoint the issue. Let me know if you need more guidance on any of these steps!