Skip to main content
If you already connected your data warehouse to Elementary but are not seeing anything in the Elementary UI, there could be several reasons. Try following these steps to troubleshoot:1. Validate elementary dbt package is deployed, working, and using the latest version
  • Refer to the dbt package installation guide, and validate that your version in packages.yml is the one mentioned there. If not, upgrade and run dbt deps. Make sure to execute dbt run --select elementary for the package tables to be created.
2. Check if the table elementary_test_results exists and has data
  • If the table does not exist - refer to the dbt package installation guide. Make sure to execute dbt run --select elementary for the package tables to be created.
  • If the table exists but has no data - Did you execute dbt test since deploying the package and creating the models?
  • If you have, make sure the table was created as an incremental table (not a regular table or view).
  • If not, there is a materialization configuration in your dbt_project.yml file that overrides the package config. Remove it, and run dbt run --select elementary --full-refresh to recreate the tables. After that run dbt test again and check if there is data.
4. Still no data in the table? Reach out to the Elementary team by starting an intercom chat from the Elementary UI.
When multiple dbt jobs run in parallel, they can contend on the same Elementary metadata artifact tables.Disable automatic metadata artifact uploads in dbt_project.yml:
dbt_project.yml
Add a separate scheduled job (daily or hourly) to upload the artifacts:
For the enable_elementary_models pattern in dbt_project.yml, see Can I disable / exclude the Elementary models?. For more context, see on-run-end hooks, Reduce on-run-end time, and Dev / prod configuration.Let us know if you run into anything — start a chat from the Elementary UI or reach us on Slack.
This error can happen because of a few reasons:
  1. Check that your elementary dbt package version is 0.12.0 or higher.
  2. Check that the user you are using to connect to your database has permission to access the information schema of all the schemas built or used by your dbt project.
For more information on the permissions required by each data warehouse:SnowflakeBigqueryRedshiftDatabricksPostgres
Elementary couldn’t tell which table the test belongs to. This usually happens with singular tests that reference more than one model or source (or none at all). Link the test to its asset by setting override_primary_test_model_id in the test’s config:
Use the model’s dbt unique_id, not its name. See Test shows no assets linked to this test for the full explanation.