Compilation Error: selector 'tag:nightly' does not match any nodes

TL;DR

No node in the project carries the tag nightly, so the tag selector matches nothing and dbt errors. Add the tag to the intended models (in dbt_project.yml folder config or model YAML), or correct the selector spelling to the tag that exists. List tagged nodes with dbt ls to prove the match before running the job.

Compilation Error: selector 'tag:nightly' does not match any nodes

Use this when

• dbt run --select tag:nightly fails with Compilation Error selector tag:nightly does not match any nodes
• the nightly job is new, or tags were recently renamed or removed
• dbt ls --resource-type model shows no nightly tag on any model

Not for this skill when

• models are tagged but in a package you did not install, run dbt deps and check again
• you meant to select by path or name, use that selector instead of a tag
• the job should tolerate empty selections, that is an orchestration choice, not a tag fix

Steps

1. Inventory current tags: run dbt ls --select with no filter is too broad, so grep the project for tags in dbt_project.yml, schema YAML, and config blocks, and run dbt ls --output json to inspect node tags in the manifest. Verify: you have the list of tags actually applied in the project.

2. Compare with nightly: look for near misses such as night, nightly_run, or tags applied only to tests or snapshots rather than models. Verify: you know whether the tag is absent or merely misspelled in the selector.

3. Apply the tag where intended: prefer folder-level config in dbt_project.yml for a whole directory, or per-model tags in YAML for a curated set. Keep one canonical spelling. Verify: the intended models carry the nightly tag in config.

4. Verify with dbt ls --select tag:nightly, then run the job command with that selector. Verify: dbt ls lists the nightly models and the run builds exactly that set.

Variant phrasings

tag exists on tests only

tag selectors match any resource type by default. Scope with --resource-type model if the job should build models, or tag the models themselves.

worked before a refactor

Moving models between folders drops folder-level tag config silently. Reapply tags at the new folder level and add a dbt ls check to CI.

Compatibility: dbt-core 1.x node selection with tag: selectors; tags set via dbt_project.yml, YAML properties, or in-file config. Applies to run, build, test, and ls.

Why it happens

Tags are just node metadata, and selectors are exact matches against the manifest. If no parsed node carries the tag, either because it was never applied or folder config stopped applying it, the selector legitimately matches zero nodes and dbt treats an empty tag selection as an error worth surfacing rather than a silent no-op job.

Edge cases / pitfalls

• Tags are case sensitive in practice across tooling; standardize on lowercase.
• A nightly job that selects nothing and succeeds silently is worse than this error; keep the error and fix the tags.
• Tagging snapshots and models with the same tag mixes commands; check what your job command actually executes for each resource type.

Provenance

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

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

Thread query: Compilation Error: selector 'tag:nightly' does not match any nodes

TL;DR: No node in the project carries the tag nightly, so the tag selector matches nothing and dbt errors. Add the tag to the intended models (in dbt_project.yml folder config or model YAML), or correct the selector spelling to the tag that exists. List tagged nodes with dbt ls to prove the match before running the job.