# CI job - Deferring to a different target than the one specified

**URL:** <https://discourse.getdbt.com/t/ci-job-deferring-to-a-different-target-than-the-one-specified/12012>\
**Category:** Help\
**Tags:** ci-cd\
**Created:** [February 12, 2024, 3:16pm UTC](https://discourse.getdbt.com/t/ci-job-deferring-to-a-different-target-than-the-one-specified/12012 "2024-02-12T15:16:52Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![KHO](https://avatars.discourse-cdn.com/v4/letter/k/eb8c5e/32.png) [@KHO](https://discourse.getdbt.com/u/KHO)\
**Post date:** [February 12, 2024, 3:16pm UTC](https://discourse.getdbt.com/t/ci-job-deferring-to-a-different-target-than-the-one-specified/12012/1 "2024-02-12T15:16:52Z")

</div>

## The problem I’m having: Im trying to run a CI job that runs on PR’s but i want to ensure that it defers to the same target as the target the user is currently working in.

For example: When i’ve ran a CI job in UAT target in QA environment, it defers to the most recent QA job run, which sometimes may be in PRD target, and so this causes issues.

## What I’ve already tried

In the CI job, i’ve tried to specify the target\_name as UAT.  
The job commands I have in the job are:

- dbt clone --select state:modified+,config.materialized:incremental,state:old
- dbt build --select state:modified+