# How to not have set\_stats pass downstream to different workflows

**URL:** <https://forum.ansible.com/t/how-to-not-have-set-stats-pass-downstream-to-different-workflows/4604>\
**Category:** Get Help\
**Created:** [March 27, 2024, 7:34pm UTC](https://forum.ansible.com/t/how-to-not-have-set-stats-pass-downstream-to-different-workflows/4604 "2024-03-27T19:34:57Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![rammarepally](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/rammarepally/32/2699_2.png) [@rammarepally](https://forum.ansible.com/u/rammarepally)\
**Post date:** [March 27, 2024, 7:34pm UTC](https://forum.ansible.com/t/how-to-not-have-set-stats-pass-downstream-to-different-workflows/4604/1 "2024-03-27T19:34:57Z")

</div>

We have a wokflow in which one node captures a list using set\_stats module and passes them downstream to the other nodes in the workflow .On success, it launches the same workflow but in a different environment but however we see the list from previous workflow being passed into the new one as extra vars . How do we avoid a variable under set\_stats to not get passed to another workflow .