# Follow up: prevent parallel builds

**URL:** <https://discuss.circleci.com/t/follow-up-prevent-parallel-builds/43803>\
**Category:** Product Feedback\
**Tags:** workflow\
**Created:** [April 24, 2022, 11:46pm UTC](https://discuss.circleci.com/t/follow-up-prevent-parallel-builds/43803 "2022-04-24T23:46:13Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![relaxdiego](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/relaxdiego/32/28083_2.png) [@relaxdiego](https://discuss.circleci.com/u/relaxdiego)\
**Post date:** [April 24, 2022, 11:46pm UTC](https://discuss.circleci.com/t/follow-up-prevent-parallel-builds/43803/1 "2022-04-24T23:46:13Z")

</div>

What’s the status of the internal feature request that was mentioned by a former CircleCI employee in this comment:

[https://discuss.circleci.com/t/prevent-concurrent-builds-of-a-branch/1142/23?u=relaxdiego](https://discuss.circleci.com/t/prevent-concurrent-builds-of-a-branch/1142/23)

It would be great if this feature was finally implemented because whatever current workarounds are presented either don’t address the requirements or use up credits unnecessarily.

For clarity, the behavior I expect to see is described under “Solution #3” of this article:

[https://www.relaxdiego.com/2022/04/sharing-environments-effectively.html](https://www.relaxdiego.com/2022/04/sharing-environments-effectively.html)
