What causes GraphDependencyNotFoundError?

A model is referenced with ref() but was renamed, deleted, or moved to a disabled package. The model being referenced is excluded by the current dbt selector. A model in a different dbt project is referenced without a cross-project ref configuration. The model exists but is in a subfolder and the path is resolved incorrectly. A recent refactoring renamed a model but not all ref() calls were updated

How do I fix GraphDependencyNotFoundError?

Run `dbt ls --select ` to confirm whether the node exists in the current compiled graph.. Search your project for `ref(' ')` to find every file that references it, then update those calls to the new model name if it was renamed.. If the model lives in a package, run `dbt deps` to reinstall packages and confirm the package is not marked `disabled: true` in packages.yml.. For cross-project refs in dbt Mesh, verify the upstream project is declared as a dependency in dependencies.yml and that the model's access level is set to `public`.. Run `dbt compile` to surface all unresolved graph dependencies before triggering the full run.

High severitycompilationdbt Cloud →

dbt Error:
GraphDependencyNotFoundError

What does this error mean?

dbt resolved all ref() and source() names successfully, but when building the execution graph, a referenced node is absent from the compiled set — typically because it was excluded by a selector, disabled in a package, or not yet installed.

Common causes

1A model is referenced with ref() but was renamed, deleted, or moved to a disabled package
2The model being referenced is excluded by the current dbt selector
3A model in a different dbt project is referenced without a cross-project ref configuration
4The model exists but is in a subfolder and the path is resolved incorrectly
5A recent refactoring renamed a model but not all ref() calls were updated

How to fix it

1Run `dbt ls --select <model_name>` to confirm whether the node exists in the current compiled graph.
2Search your project for `ref('<missing_model>')` to find every file that references it, then update those calls to the new model name if it was renamed.
3If the model lives in a package, run `dbt deps` to reinstall packages and confirm the package is not marked `disabled: true` in packages.yml.
4For cross-project refs in dbt Mesh, verify the upstream project is declared as a dependency in dependencies.yml and that the model's access level is set to `public`.
5Run `dbt compile` to surface all unresolved graph dependencies before triggering the full run.

Frequently asked questions

How do I find all ref() calls to a specific model?

Search your project for ref('<model_name>') using grep or your IDE's search function. dbt ls --select +<model_name> also shows all downstream dependents.

Can I ref() a model from another dbt project?

Yes, in dbt Cloud with Enterprise multi-project setups. In dbt Core, cross-project refs require manual configuration.

Source · docs.getdbt.com/reference/exceptions