dbt troubleshooting

This page covers common issues with dbt project configuration and execution in Adverity.

Repository connection issues

If Adverity cannot connect to or clone your repository, verify that:

• The public key is added as a deploy key in your repository.

• The branch name is correct and exists (if specified).

• The path to dbt_project.yml is correct and the file exists (if specified).

Missing profile property in dbt_project.yml

Symptoms: Job run fails even though the warehouse and repository are correctly configured.

Cause: The profile property is missing from dbt_project.yml. Adverity reads this property to generate the profiles.yml file. If it is absent, the job run fails regardless of the warehouse configuration.

Resolution: Add a profile property to your dbt_project.yml, for example:

profile: my_project

Profile name mismatch when using a custom dbt_project.yml path

Symptoms: Job run fails when using an Adverity-managed warehouse together with a custom path to dbt_project.yml configured in the project settings.

Cause: When using an Adverity-managed profile, the profile name in the generated profiles.yml is based on the dbt_project.yml found during the automatic tree search, not the file at your specified path. If the two files define different profile names, dbt cannot match them and the job run fails.

Resolution: Ensure that the profile property in the dbt_project.yml at your specified path matches the profile property in the first dbt_project.yml found by the automatic tree search.