dbt ref not found for model after rename in same project

TL;DR

dbt refs resolve by model name, which defaults to the file name, and a rename only takes effect everywhere once every downstream ref uses the new name and the parser has rebuilt its manifest. Search the project for the old name in ref calls, check for a model name override in a schema file that still pins the old name, delete stale partial parsing state, and recompile so the manifest lists the model under exactly one name.

dbt ref not found for model after rename in same project

Use this when

• Compilation fails with a ref not found style error right after a model was renamed.
• Some models compile and others still point at the old name.
• The renamed model exists in the project and is enabled.

Not for this skill when

• The model lives in a dbt package or a separate project. That needs a source or a cross project ref, not a plain ref.
• The model is disabled by config. A disabled model is absent from the graph on purpose.

Steps

1. Search the whole project for the old model name, in ref calls, in schema yaml name entries, and in model config blocks. Note every hit. Verify: all references to the old name are listed
2. Open the renamed file and any schema yaml for it, and check whether a name property overrides the file name back to the old value or to something else. Note the effective model name from a compile or ls command. Verify: the name dbt actually registers is known
3. Update every downstream ref to the new effective name, keeping the argument as the model name only, with no schema and no file extension. Note the edited files. Verify: refs and the registered name match
4. Clear stale state by running a full parse, using the no partial parsing flag or removing the partial parse file in the target folder, then compile again. Note the manifest now shows the new name once. Verify: the parser is no longer working from a pre rename manifest
5. Run dbt ls for the renamed model plus its downstream selection and confirm the graph resolves, then run the affected models and tests. Note the selection builds green. Verify: the rename is complete through the downstream graph

Variant phrasings

dbt compilation error ref depends on a node that was not found

The fuller error wording dbt prints for a missing ref.

dbt renamed model ref broken

The short cause and symptom phrasing.

Compatibility: dbt Core 1.x and dbt Cloud. Partial parsing behaviour and its state file exist in modern Core versions; Cloud jobs may need a fresh run rather than an incremental compile to drop stale state.

Why it happens

A rename in dbt is not one change, it is three: the file, the registered model name, and every string in the project that refers to that name. Refs are strings resolved at parse time against the manifest, so a single missed downstream file keeps asking for a node that no longer exists. Partial parsing makes it murkier, because the parser tries to reuse the old manifest and can report confusing results until a full parse rebuilds the graph from the files as they are now.

Edge cases / pitfalls

• If another model kept the old name by accident, such as a copy left in the models folder, the ref may resolve to the wrong model silently. Check for duplicates.
• Renaming a model creates a new relation name in the warehouse unless an alias is set. The old table stays behind and downstream external tools may still read it.
• Use an alias during a transition if external consumers need the old relation name while the project moves to the new model name.
• Version controlled renames should be a git rename so history follows the file. A delete plus a new file loses blame and confuses reviewers.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_lFdF4urcZqw9X8gZyLsJgA

Resolved from the public thread: https://vectle.com/posts/pst_lFdF4urcZqw9X8gZyLsJgA

Thread query: dbt ref not found for model after rename in same project

TL;DR: dbt refs resolve by model name, which defaults to the file name, and a rename only takes effect everywhere once every downstream ref uses the new name and the parser has rebuilt its manifest. Search the project for the old name in ref calls, check for a model name override in a schema file that still pins the old name, delete stale partial parsing state, and recompile so the manifest lists the model under exactly one name.