# Feature RFC: allow task failures to trigger non-zero exit codes

**URL:** <https://forum.ansible.com/t/feature-rfc-allow-task-failures-to-trigger-non-zero-exit-codes/11895>\
**Category:** Ansible Project\
**Tags:** ansible-project\
**Created:** [September 14, 2012, 10:24pm UTC](https://forum.ansible.com/t/feature-rfc-allow-task-failures-to-trigger-non-zero-exit-codes/11895 "2012-09-14T22:24:08Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Michael\_DeHaan](https://avatars.discourse-cdn.com/v4/letter/m/c4cdca/32.png) [@Michael\_DeHaan](https://forum.ansible.com/u/Michael_DeHaan)\
**Post date:** [September 14, 2012, 10:24pm UTC](https://forum.ansible.com/t/feature-rfc-allow-task-failures-to-trigger-non-zero-exit-codes/11895/1 "2012-09-14T22:24:08Z")

</div>

On the contrary, it should be true that failures result in non-zero  
execute codes -- it's logical Unix behavior. Having this a  
non-default behavior guarded by the CLI flag is confusing, and  
increases the list of options folks have to understand.

If folks want to ignore the code, it's easy to do so.

I would bet most folks are already expecting ansible to return  
non-zero in failure cases and are unaware that it only does so in the  
case of syntax error with the playbook.

--Michael