# selectors.yaml not matching CLI --select behavior

**URL:** <https://discourse.getdbt.com/t/selectors-yaml-not-matching-cli-select-behavior/8167>\
**Category:** Help\
**Created:** [May 5, 2023, 6:07pm UTC](https://discourse.getdbt.com/t/selectors-yaml-not-matching-cli-select-behavior/8167 "2023-05-05T18:07:24Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![mark.shapiro](https://sea2.discourse-cdn.com/flex020/user_avatar/discourse.getdbt.com/mark.shapiro/32/2783_2.png) [@mark.shapiro](https://discourse.getdbt.com/u/mark.shapiro)\
**Post date:** [May 5, 2023, 6:07pm UTC](https://discourse.getdbt.com/t/selectors-yaml-not-matching-cli-select-behavior/8167/1 "2023-05-05T18:07:24Z")

</div>

## The problem I’m having

I am unsure if there is a bug or we do not know how to use selectors.yaml. It will not do compound selections correctly and when creating multiple named selectors, only the first one runs.

## The context of why I’m trying to do this

The ability to create selectors based on multiple tags instead of just folder paths

 ![dbt_selectors_error](https://us1.discourse-cdn.com/flex020/uploads/getdbt/original/2X/8/8bcb8038165dd31be4657b7c35611dab5a9bb33b.png)

Trying either the CLI format or full yaml format (with cautious or buildable) yields different results from what normal --select returns.