# '@' model selector and defer interaction

**URL:** <https://discourse.getdbt.com/t/model-selector-and-defer-interaction/20621>\
**Category:** Help\
**Tags:** node-selection\
**Created:** [March 9, 2026, 10:56am UTC](https://discourse.getdbt.com/t/model-selector-and-defer-interaction/20621 "2026-03-09T10:56:34Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Izaak](https://avatars.discourse-cdn.com/v4/letter/i/bc79bd/32.png) [@Izaak](https://discourse.getdbt.com/u/Izaak)\
**Post date:** [March 9, 2026, 10:56am UTC](https://discourse.getdbt.com/t/model-selector-and-defer-interaction/20621/1 "2026-03-09T10:56:34Z")

</div>

Hi dbt-community!

I was wondering how the ‘@’ node selection operator interacts with the --defer flag.

Take this example from the dbt docs:

 ![db-@-selector-graph](https://us1.discourse-cdn.com/flex020/uploads/getdbt/original/2X/e/e333230ec722161934369ca7f265fce41f858adf.png)

Here, `dbt run --select @snowplow_web_page_context`, will run all models shown in the image.

I could achieve the same result with defer:  
`dbt run --select snowplow_web_page_context+ --defer --state 'path-to-manifest-where-snowplow_base_events-exists'`

But what if I do both? :  
`dbt run --select @snowplow_web_page_context --defer --state 'path-to-manifest-where-snowplow_base_events-exists'`  
What takes precedence, `defer`, `@` or some mix?

Thanks!