# Recovering from failure in handlers

**URL:** <https://forum.ansible.com/t/recovering-from-failure-in-handlers/18184>\
**Category:** Ansible Project\
**Created:** [May 7, 2015, 2:25pm UTC](https://forum.ansible.com/t/recovering-from-failure-in-handlers/18184 "2015-05-07T14:25:01Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Shawn\_Ferry](https://avatars.discourse-cdn.com/v4/letter/s/f0a364/32.png) [@Shawn\_Ferry](https://forum.ansible.com/u/Shawn_Ferry)\
**Post date:** [May 7, 2015, 2:25pm UTC](https://forum.ansible.com/t/recovering-from-failure-in-handlers/18184/1 "2015-05-07T14:25:01Z")

</div>

I’ve recently experienced the case where a handler has failed stopping the remaining handler execution in a playbook.

Once the triggering change has completed subsequent playbook execution will not notify the handlers again even if they didn’t finish the last time.

Is there any way to capture the handlers which would have been run and run them on a subsequent playbook execution? Clearly the best thing would be not failing in the first place but I can’t always ensure that will be the case.

---

<div class="post-metadata">

**Author:** ![vaida.dan](https://avatars.discourse-cdn.com/v4/letter/v/5daacb/32.png) [@vaida.dan](https://forum.ansible.com/u/vaida.dan)\
**Post date:** [July 21, 2015, 1:18pm UTC](https://forum.ansible.com/t/recovering-from-failure-in-handlers/18184/2 "2015-07-21T13:18:27Z")

</div>

you can try _ignore\_errors: yes_ in your handler.