# lookup plugins eating exceptions?

**URL:** <https://forum.ansible.com/t/lookup-plugins-eating-exceptions/15091>\
**Category:** Ansible Project\
**Created:** [April 25, 2014, 2:34pm UTC](https://forum.ansible.com/t/lookup-plugins-eating-exceptions/15091 "2014-04-25T14:34:44Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Scott\_Anderson](https://avatars.discourse-cdn.com/v4/letter/s/ed655f/32.png) [@Scott\_Anderson](https://forum.ansible.com/u/Scott_Anderson)\
**Post date:** [April 25, 2014, 2:34pm UTC](https://forum.ansible.com/t/lookup-plugins-eating-exceptions/15091/1 "2014-04-25T14:34:44Z")

</div>

I had to add some try/catch logic in template.py to discover that there was an issue with the template I was using in lookup(‘template’). The plugin was just returning empty string due to the template error.

Are the lookup plugins supposed to eat exceptions?

Regards,  
-scott

---

<div class="post-metadata">

**Author:** ![Michael\_DeHaan1](https://avatars.discourse-cdn.com/v4/letter/m/5e9695/32.png) [@Michael\_DeHaan1](https://forum.ansible.com/u/Michael_DeHaan1)\
**Post date:** [April 25, 2014, 8:52pm UTC](https://forum.ansible.com/t/lookup-plugins-eating-exceptions/15091/2 "2014-04-25T20:52:23Z")

</div>

Lookup plugins not raising exceptions is a known issue at the moment – though I’m not positive there’s a ticket. Please see if there is one and if not please file it.