# Cancel workflows started by Bitrise Start Build in a build that has been canceled

**URL:** <https://discuss.bitrise.io/t/cancel-workflows-started-by-bitrise-start-build-in-a-build-that-has-been-canceled/10184>\
**Category:** Steps\
**Created:** [September 12, 2019, 6:56pm UTC](https://discuss.bitrise.io/t/cancel-workflows-started-by-bitrise-start-build-in-a-build-that-has-been-canceled/10184 "2019-09-12T18:56:14Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![dicksson.oliveira](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/dicksson.oliveira/32/2397_2.png) [@dicksson.oliveira](https://discuss.bitrise.io/u/dicksson.oliveira)\
**Post date:** [September 12, 2019, 6:56pm UTC](https://discuss.bitrise.io/t/cancel-workflows-started-by-bitrise-start-build-in-a-build-that-has-been-canceled/10184/1 "2019-09-12T18:56:14Z")

</div>

## Description of the feature request

There should be a way to automatically cancel workflows that have been started by the _Bitrise Start Build_ step if the workflow is aborted/fails during the _Bitrise Wait for Build_.

## Use case / for what or how I would use it

When workflow `primary` executes the _Bitrise Start Build_ step and hangs in the _Bitrise Wait for Build_ step, and if rolling builds are enabled, when a new build is triggered, the `primary` workflow is aborted but the started builds keep running. This is not ideal, since the new `primary` workflow is put on hold because the secondary workflows are using the available concurrencies.

---

<div class="post-metadata">

**Author:** ![Roland-Bak](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/roland-bak/32/3480_2.png) [@Roland-Bak](https://discuss.bitrise.io/u/Roland-Bak)\
**Post date:** [September 13, 2019, 12:54pm UTC](https://discuss.bitrise.io/t/cancel-workflows-started-by-bitrise-start-build-in-a-build-that-has-been-canceled/10184/2 "2019-09-13T12:54:00Z")

</div>

Hi there @dicksson.oliveira 👋

Thanks for the feature request! 🙂  
Make sure to vote on it 😉

---

<div class="post-metadata">

**Author:** ![vvereckei](https://avatars.discourse-cdn.com/v4/letter/v/9de0a6/32.png) [@vvereckei](https://discuss.bitrise.io/u/vvereckei)\
**Post date:** [October 22, 2019, 11:54am UTC](https://discuss.bitrise.io/t/cancel-workflows-started-by-bitrise-start-build-in-a-build-that-has-been-canceled/10184/3 "2019-10-22T11:54:52Z")

</div>

This would be awesome to have.

Piggybacking on the feature request : If the primary workflow is able to cancel all child workflows it triggered, it would be really handy to have an option to enable this for certain workflows.  
Currently under the app settings there is an option **Will cancel all previous builds for Pushes to the same branch** which seems to not affect our Bitrise Start Build workflows.

Adding another option there to enable/disable build stop on code push for certain workflows (the primary ones that are triggering all other in our case) would save a lot on build time and allow us to get rid of unnecessary concurrent builds.