# Dvc repro --force-downstream not working

**URL:** <https://discuss.dvc.org/t/dvc-repro-force-downstream-not-working/1122>\
**Category:** Questions\
**Created:** [March 16, 2022, 11:49pm UTC](https://discuss.dvc.org/t/dvc-repro-force-downstream-not-working/1122 "2022-03-16T23:49:16Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Buffy](https://avatars.discourse-cdn.com/v4/letter/b/22d042/32.png) [@Buffy](https://discuss.dvc.org/u/Buffy)\
**Post date:** [March 16, 2022, 11:49pm UTC](https://discuss.dvc.org/t/dvc-repro-force-downstream-not-working/1122/1 "2022-03-16T23:49:16Z")

</div>

Hi,

I setup some dvc data pipeline and use dvc repro command generated some .pkl files. I later on decided to regenerate the files (due to code change, where the dependency wasn’t captured in the dvc.yaml file), so I deleted the file manually in the directory. This is probably the first mistake I made.

So now when I run dvc repro, dvc refuse to re-run and report nothing has been change.

I thought dvc repro --force-downstream [target] should work, but it’s still reporting “everything is up to date” and not reproducing the stage.

How do I force dvc to re-run the stage to regenerate the .pkl file?

Thanks,

---

<div class="post-metadata">

**Author:** ![dtrifiro](https://avatars.discourse-cdn.com/v4/letter/d/278dde/32.png) [@dtrifiro](https://discuss.dvc.org/u/dtrifiro)\
**Post date:** [March 17, 2022, 10:17am UTC](https://discuss.dvc.org/t/dvc-repro-force-downstream-not-working/1122/2 "2022-03-17T10:17:56Z")

</div>

Hi,  
would you mind sharing your `dvc.yaml`? Did you add the output `pkl` files as stage outputs?

---

<div class="post-metadata">

**Author:** ![Buffy](https://avatars.discourse-cdn.com/v4/letter/b/22d042/32.png) [@Buffy](https://discuss.dvc.org/u/Buffy)\
**Post date:** [March 17, 2022, 11:36pm UTC](https://discuss.dvc.org/t/dvc-repro-force-downstream-not-working/1122/3 "2022-03-17T23:36:28Z")

</div>

Hi,

Short answer is yes. Please see the train and test stages from my dvc.yaml below.

training:  
cmd: python3 code/train.py  
params:  
- train  
deps:  
- ./data/SWT\_transform/Hisar\_test\_data\_firstOrder.npy  
- ./data/SWT\_transform/Hisar\_test\_data\_secondOrder.npy  
- ./data/SWT\_transform/Hisar\_test\_data\_total.npy  
- ./data/SWT\_transform/Hisar\_train\_data\_firstOrder.npy  
- ./data/SWT\_transform/Hisar\_train\_data\_secondOrder.npy  
- ./data/SWT\_transform/Hisar\_train\_data\_total.npy  
outs:  
- ./model/rbf\_svm\_3\_.pkl #The model ID needs to be updated for each new model generated  
- ./model/scaler3.bin

test:  
cmd: python3 code/test.py  
params:  
- test  
deps:  
- ./model/rbf\_svm\_3\_.pkl  
- ./model/scaler3.bin

---

<div class="post-metadata">

**Author:** ![dtrifiro](https://avatars.discourse-cdn.com/v4/letter/d/278dde/32.png) [@dtrifiro](https://discuss.dvc.org/u/dtrifiro)\
**Post date:** [March 18, 2022, 9:01am UTC](https://discuss.dvc.org/t/dvc-repro-force-downstream-not-working/1122/4 "2022-03-18T09:01:18Z")

</div>

Thanks! The pipeline itself looks fine, but you might want to add `code/train.py` to dependencies. That way, when you change `train.py` and run `dvc repro`, the `training` stage will be re-run since one of its dependencies changed.

To force reproducing without adding `train.py` you could use `dvc repro -f`