# Same $BITRISE\_BUILD\_NUMBER is assigned to 2 different builds

**URL:** <https://discuss.bitrise.io/t/same-bitrise-build-number-is-assigned-to-2-different-builds/18667>\
**Category:** Question & Answer\
**Created:** [November 18, 2021, 12:30am UTC](https://discuss.bitrise.io/t/same-bitrise-build-number-is-assigned-to-2-different-builds/18667 "2021-11-18T00:30:54Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ryu.0](https://avatars.discourse-cdn.com/v4/letter/r/aca169/32.png) [@Ryu.0](https://discuss.bitrise.io/u/Ryu.0)\
**Post date:** [November 18, 2021, 12:30am UTC](https://discuss.bitrise.io/t/same-bitrise-build-number-is-assigned-to-2-different-builds/18667/1 "2021-11-18T00:30:54Z")

</div>

I have notices branch and its pr have same build number:

 ![Screen Shot 2021-11-18 at 9.30.22 AM](https://us1.discourse-cdn.com/flex016/uploads/bitrise/original/2X/c/c57f2a2acaa9c919a73bc138ad189dc45b73eecc.jpeg)

Any ideas to make sure it always gets incremented ?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/bitrise/original/2X/d/d901cf2aad020f2dd11918afc89ec2089bb87b35.png) [@system](https://discuss.bitrise.io/u/system)\
**Post date:** [December 18, 2021, 12:31am UTC](https://discuss.bitrise.io/t/same-bitrise-build-number-is-assigned-to-2-different-builds/18667/2 "2021-12-18T00:31:21Z")

</div>

Closed on December 18, 2021, 12:31am UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

---

<div class="post-metadata">

**Author:** ![nate.risenhoover](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/nate.risenhoover/32/4713_2.png) [@nate.risenhoover](https://discuss.bitrise.io/u/nate.risenhoover)\
**Post date:** [December 22, 2021, 4:19pm UTC](https://discuss.bitrise.io/t/same-bitrise-build-number-is-assigned-to-2-different-builds/18667/3 "2021-12-22T16:19:36Z")

</div>

Hi there 👋

Generally, your build numbers should be unique. We have seen some issues like this where they may be the same due to a very small time window.

We have a ticket open internally to investigate ths.
