# Pipeline timeouts

**URL:** <https://forum.buildkite.community/t/pipeline-timeouts/722>\
**Category:** Features Requests\
**Created:** [October 3, 2019, 5:17pm UTC](https://forum.buildkite.community/t/pipeline-timeouts/722 "2019-10-03T17:17:01Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![haraldschioberg](https://avatars.discourse-cdn.com/v4/letter/h/f1d935/32.png) [@haraldschioberg](https://forum.buildkite.community/u/haraldschioberg)\
**Post date:** [October 3, 2019, 5:17pm UTC](https://forum.buildkite.community/t/pipeline-timeouts/722/1 "2019-10-03T17:17:01Z")

</div>

Can pipelines have a timeout? That way jobs with unmatched “agent” rules, or unmatched dependencies ([Build stays in 'Running' forever for `depends_on: ["\<unknown\>"]`](https://forum.buildkite.community/t/build-stays-in-running-forever-for-depends-on-unknown/711)) would be reaped after some time.

---

<div class="post-metadata">

**Author:** ![Keith](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.buildkite.community/keith/32/592_2.png) [@Keith](https://forum.buildkite.community/u/Keith)\
**Post date:** [October 3, 2019, 5:42pm UTC](https://forum.buildkite.community/t/pipeline-timeouts/722/2 "2019-10-03T17:42:56Z")

</div>

+1 this would be great. We have this case quite often where we maintain a macOS fleet with specific versions of Xcode for iOS builds, and if someone pushes to a very old branch we have jobs that will never start that are misleading to the developers and end up running indefinitely.