What causes SelectorError?

A model or tag name in the --select expression was renamed or deleted but the dbt Cloud job definition was not updated. The selector uses a method (e.g., `config.materialized:`, `exposure:`) that requires a dbt version newer than what is installed. A YAML selector file (selectors.yml) has a syntax error or references a non-existent node. The `+` or `@` graph operator is used incorrectly — e.g., `++model` instead of `+model`. A package prefix in the selector (e.g., `package.model_name`) does not match the actual package name in packages.yml

How do I fix SelectorError?

Run `dbt ls --select ` locally to validate the selector without running any models.. Check that all model names, tags, and source names in the selector exist in the current project: `dbt ls --resource-type model`.. Review the dbt selector syntax documentation for the dbt version in use — selector methods added in later versions are not available in older environments.. If using a selectors.yml file, run `dbt parse` to validate the file syntax before triggering the job.. Update the dbt Cloud job definition if a model referenced in the --select argument was renamed or removed from the project.

Low severityconfiguration

Power BI Refresh Error:
SelectorError

What does this error mean?

dbt could not parse or resolve the node selection expression passed via --select, --exclude, or --selector. The run fails immediately with a SelectorError before any models execute. This error is caused by invalid selector syntax, references to nodes that do not exist in the project, or use of selector methods that are not supported by the installed dbt version.

Common causes

1A model or tag name in the --select expression was renamed or deleted but the dbt Cloud job definition was not updated
2The selector uses a method (e.g., `config.materialized:`, `exposure:`) that requires a dbt version newer than what is installed
3A YAML selector file (selectors.yml) has a syntax error or references a non-existent node
4The `+` or `@` graph operator is used incorrectly — e.g., `++model` instead of `+model`
5A package prefix in the selector (e.g., `package.model_name`) does not match the actual package name in packages.yml

How to fix it

1Run `dbt ls --select <expression>` locally to validate the selector without running any models.
2Check that all model names, tags, and source names in the selector exist in the current project: `dbt ls --resource-type model`.
3Review the dbt selector syntax documentation for the dbt version in use — selector methods added in later versions are not available in older environments.
4If using a selectors.yml file, run `dbt parse` to validate the file syntax before triggering the job.
5Update the dbt Cloud job definition if a model referenced in the --select argument was renamed or removed from the project.

Frequently asked questions

How do I test a selector without running any models?

Use `dbt ls --select <expression>` — this lists all nodes that would be selected without executing any SQL. It's the fastest way to validate selector syntax.

Can I use wildcards in dbt selectors?

Yes — the `*` wildcard matches any string within a node name component: `--select staging_*` selects all models starting with `staging_`. Wildcards work within the same selector method (name, tag, source).