# Possible bug using inlcude and tags ?

**URL:** <https://forum.ansible.com/t/possible-bug-using-inlcude-and-tags/12485>\
**Category:** Ansible Project\
**Tags:** ansible-project\
**Created:** [March 12, 2013, 1:55pm UTC](https://forum.ansible.com/t/possible-bug-using-inlcude-and-tags/12485 "2013-03-12T13:55:07Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Michael\_DeHaan2](https://avatars.discourse-cdn.com/v4/letter/m/da6949/32.png) [@Michael\_DeHaan2](https://forum.ansible.com/u/Michael_DeHaan2)\
**Post date:** [March 12, 2013, 1:55pm UTC](https://forum.ansible.com/t/possible-bug-using-inlcude-and-tags/12485/1 "2013-03-12T13:55:07Z")

</div>

Yeah I would not consider this a bug, but a limitation in the way tags work.

Because the other task wasn't tagged, it doesn't know what value to  
use for the conditional. You could tag it something else, but you  
would have to set it.

You could also technically fix this with changing to an 'only\_if' (a  
little more syntax) and checking if it was set first before checking  
if failed.

Should look something like this:

only\_if: 'is\_set($installed) and is\_failed($installed)'