# Two workflows triggered on the same branch

**URL:** <https://discuss.bitrise.io/t/two-workflows-triggered-on-the-same-branch/3409>\
**Category:** Released\
**Created:** [November 30, 2017, 5:08pm UTC](https://discuss.bitrise.io/t/two-workflows-triggered-on-the-same-branch/3409 "2017-11-30T17:08:07Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![johnpeb](https://avatars.discourse-cdn.com/v4/letter/j/5daacb/32.png) [@johnpeb](https://discuss.bitrise.io/u/johnpeb)\
**Post date:** [November 30, 2017, 5:08pm UTC](https://discuss.bitrise.io/t/two-workflows-triggered-on-the-same-branch/3409/1 "2017-11-30T17:08:07Z")

</div>

Hi, we have two apps being built from a single iOS codebase on the same branch. These two apps are currently two different workflows and we’ve identified two issues:

- rolling builds consider them to be the same and one is cancelled when the other is queued up manually.
- it’s not possible to configure triggers for multiple workflows for a single branch.

Now I assume we could merge the workflows but with this dual workflow config, builds would be available sooner so seem preferred. Also more scalable if we want to have more than two apps.

---

<div class="post-metadata">

**Author:** ![koral](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/koral/32/357_2.png) [@koral](https://discuss.bitrise.io/u/koral)\
**Post date:** [November 30, 2017, 6:39pm UTC](https://discuss.bitrise.io/t/two-workflows-triggered-on-the-same-branch/3409/2 "2017-11-30T18:39:11Z")

</div>

It seems that there is already feature request for this: [Parallel Builds: Seperate stacks for seperate workflows + trigger multiple workflows (builds) at the same time](http://discuss.bitrise.io/t/parallel-builds-seperate-stacks-for-seperate-workflows-trigger-multiple-workflows-builds-at-the-same-time/410)

As well as how to: [How to trigger multiple workflows at the same time](http://discuss.bitrise.io/t/how-to-trigger-multiple-workflows-at-the-same-time/3401)

---

<div class="post-metadata">

**Author:** ![viktorbenei](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/viktorbenei/32/18_2.png) [@viktorbenei](https://discuss.bitrise.io/u/viktorbenei)\
**Post date:** [December 1, 2017, 9:19am UTC](https://discuss.bitrise.io/t/two-workflows-triggered-on-the-same-branch/3409/3 "2017-12-01T09:19:25Z")

</div>

@johnpeb thanks for the #feature-request! @koral is right, there’s already an existing #feature-request which covers most of what you described, but I’ll migrate your message there to have it in that context. Feel free to vote on that #feature-request! 🙂

---

<div class="post-metadata">

**Author:** ![viktorbenei](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/viktorbenei/32/18_2.png) [@viktorbenei](https://discuss.bitrise.io/u/viktorbenei)\
**Post date:** [December 1, 2017, 9:19am UTC](https://discuss.bitrise.io/t/two-workflows-triggered-on-the-same-branch/3409/4 "2017-12-01T09:19:41Z")

</div>

A post was merged into an existing topic: [Parallel Builds: Seperate stacks for seperate workflows + trigger multiple workflows (builds) at the same time](https://discuss.bitrise.io/t/parallel-builds-seperate-stacks-for-seperate-workflows-trigger-multiple-workflows-builds-at-the-same-time/410)

---

<div class="post-metadata">

**Author:** ![viktorbenei](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/viktorbenei/32/18_2.png) [@viktorbenei](https://discuss.bitrise.io/u/viktorbenei)\
**Post date:** [December 1, 2017, 9:20am UTC](https://discuss.bitrise.io/t/two-workflows-triggered-on-the-same-branch/3409/5 "2017-12-01T09:20:44Z")

</div>