# Set a lower timeout for projects
**URL:** https://discuss.bitrise.io/t/set-a-lower-timeout-for-projects/1586
**Category:** Released
**Tags:** released
**Created:** [April 27, 2017, 8:35pm UTC](https://discuss.bitrise.io/t/set-a-lower-timeout-for-projects/1586 "2017-04-27T20:35:39Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@alcarvalho](https://discuss.bitrise.io/u/alcarvalho)
#### Post date: [April 27, 2017, 8:35pm UTC](https://discuss.bitrise.io/t/set-a-lower-timeout-for-projects/1586/1 "2017-04-27T20:35:39Z")
I know that builds have a default timeout based on the tier. But I know that my project doesn’t take more than X minutes to build and when that happens it’s because something is wrong. I’d rather have a setting for each project so the build is aborted sooner.
---
### Author:  [@viktorbenei](https://discuss.bitrise.io/u/viktorbenei)
#### Post date: [April 28, 2017, 8:28am UTC](https://discuss.bitrise.io/t/set-a-lower-timeout-for-projects/1586/2 "2017-04-28T08:28:46Z")
Awesome idea @alcarvalho! Don’t forget to vote on it! 😉
Note: a related feature is already on the way, although it was delayed quite a bit now… Basically that you could mark steps on the UI / in `bitrise.yml` with a `timeout` parameter, aborting that specific step if it exceeds its max execution time.
This could solve the issue you described, although might require a bit more configuration than just specifying a single timeout for every build of the app. On the other hand this will allow more granular control over the timeout.
Maybe we could extend that with a global `timeout` and maybe with a per-workflow `timeout` parameter, to help with non step specific timeouts / max exec time.
What do you think @alcarvalho?
---
### Author:  [@alcarvalho](https://discuss.bitrise.io/u/alcarvalho)
#### Post date: [April 28, 2017, 12:21pm UTC](https://discuss.bitrise.io/t/set-a-lower-timeout-for-projects/1586/3 "2017-04-28T12:21:10Z")
Well, a timeout for each step would already solve the problem, in my opinion. In my experience, it’s usually just one step that’s more time consuming and prone to having these random problems that will timeout the whole build anyway.
Having a global timeout per workflow would definitely be more convenient to setup, but I’d be happy either way and I guess a per step set is more flexible. Looking forward to that feature!
---
### Author:  [@viktorbenei](https://discuss.bitrise.io/u/viktorbenei)
#### Post date: [April 28, 2017, 2:03pm UTC](https://discuss.bitrise.io/t/set-a-lower-timeout-for-projects/1586/4 "2017-04-28T14:03:56Z")
> [@alcarvalho](#):
>
> it’s usually just one step that’s more time consuming and prone to having these random problems that will timeout the whole build anyway.
That’s our experience too, that’s why we plan(ned) to do it per-step, in the build config. Glad to hear you can confirm our speculation 😉
> [@alcarvalho](#):
>
> Looking forward to that feature!
Me too! It was already started, but we had some technical difficulties and then priorities shifted… Hopefully we can get back to finishing this soon!
---
### Author:  [@viktorbenei](https://discuss.bitrise.io/u/viktorbenei)
#### Post date: [September 22, 2017, 4:02pm UTC](https://discuss.bitrise.io/t/set-a-lower-timeout-for-projects/1586/5 "2017-09-22T16:02:00Z")
Per step `timeout` was released in the latest CLI (1.9.0) 🎉
> [@Monthly release of Bitrise CLI tools and summary of updates (September, 2017) - CLI v1.9.0](http://discuss.bitrise.io/t/monthly-release-of-bitrise-cli-tools-and-summary-of-updates-september-2017-cli-v1-9-0/2681):
>
> We ship a new bitrise cli version on the second Tuesday of every month. The new release will be available on the [bitrise.io](https://www.bitrise.io) virtual machines on the weekend after the CLI release, unless we discover a serious bug / regression. Read on to learn more about this month’s [Bitrise CLI](https://github.com/bitrise-io/bitrise) release and about the changes around bitrise tools and steps. New version of Bitrise CLI ([1.9.0](https://github.com/bitrise-io/bitrise/releases/tag/1.9.0)) step timeout handling From this bitrise version on you can specify the step’s timeout property to restrict the step…
Thanks @alcarvalho for creating this #Feature Requests and for everyone who voted on it! 🙂
---
### Author:  [@viktorbenei](https://discuss.bitrise.io/u/viktorbenei)
#### Post date: [March 25, 2018, 4:00pm UTC](https://discuss.bitrise.io/t/set-a-lower-timeout-for-projects/1586/6 "2018-03-25T16:00:01Z")
This topic was automatically closed after 14 days. New replies are no longer allowed.