# Force Build even if one content file causes issues

**URL:** <https://discourse.gohugo.io/t/force-build-even-if-one-content-file-causes-issues/3692>\
**Category:** support\
**Created:** [July 16, 2016, 12:13pm UTC](https://discourse.gohugo.io/t/force-build-even-if-one-content-file-causes-issues/3692 "2016-07-16T12:13:04Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![JeffStroudGTB](https://avatars.discourse-cdn.com/v4/letter/j/e274bd/32.png) [@JeffStroudGTB](https://discourse.gohugo.io/u/JeffStroudGTB)\
**Post date:** [July 16, 2016, 12:13pm UTC](https://discourse.gohugo.io/t/force-build-even-if-one-content-file-causes-issues/3692/1 "2016-07-16T12:13:04Z")

</div>

Hi everyone!

Basically I need a way to force Hugo to build a site even if one content file causes issues (and obviously just not build that file :D) or at the very least know how to add error handling to a heroku buildpack so that it doesn’t deploy. Because here’s my situation. I have a few people that update content but sometimes they make mistakes and they aren’t very technical, which causes problems when it breaks because I have to go in a fix it and the whole site goes down. If only the one page went down that would be awesome but currently it errors out and deploys a website that doesn’t work at all making all content unaccessible.

If anyone has any insight into a force build or something that would be awesome!!!

Thanks,

Jeff

---

<div class="post-metadata">

**Author:** ![bep](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.gohugo.io/bep/32/3332_2.png) [@bep](https://discourse.gohugo.io/u/bep)\
**Post date:** [July 16, 2016, 1:45pm UTC](https://discourse.gohugo.io/t/force-build-even-if-one-content-file-causes-issues/3692/2 "2016-07-16T13:45:21Z")

</div>

From Hugo 0.16 any breaking error exits with an errorcode != 0

---

<div class="post-metadata">

**Author:** ![JeffStroudGTB](https://avatars.discourse-cdn.com/v4/letter/j/e274bd/32.png) [@JeffStroudGTB](https://discourse.gohugo.io/u/JeffStroudGTB)\
**Post date:** [July 19, 2016, 8:43am UTC](https://discourse.gohugo.io/t/force-build-even-if-one-content-file-causes-issues/3692/3 "2016-07-19T08:43:59Z")

</div>

Perfect, thanks.

Also is there planned or maybe something to implement a force build, where content files aren’t built but the rest of the site is?

Thanks again!

Jeff

---

<div class="post-metadata">

**Author:** ![bep](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.gohugo.io/bep/32/3332_2.png) [@bep](https://discourse.gohugo.io/u/bep)\
**Post date:** [July 19, 2016, 9:10am UTC](https://discourse.gohugo.io/t/force-build-even-if-one-content-file-causes-issues/3692/4 "2016-07-19T09:10:41Z")

</div>

> [@JeffStroudGTB](#):
>
> Also is there planned or maybe something to implement a force build, where content files aren’t built but the rest of the site is?

No plans. The definition of “broken” gets adjusted over time, but broken is broken …

---

<div class="post-metadata">

**Author:** ![JeffStroudGTB](https://avatars.discourse-cdn.com/v4/letter/j/e274bd/32.png) [@JeffStroudGTB](https://discourse.gohugo.io/u/JeffStroudGTB)\
**Post date:** [July 24, 2016, 11:07am UTC](https://discourse.gohugo.io/t/force-build-even-if-one-content-file-causes-issues/3692/5 "2016-07-24T11:07:51Z")

</div>

Oh wow I realize that I just said something incorrect here. I meant to say if one content file is broken just don’t render it but still render the rest of the content files that work. But I assume the answer is the same unfortunately. Thanks for the answers though.