# recap of failed tasks

**URL:** <https://forum.ansible.com/t/recap-of-failed-tasks/14366>\
**Category:** Ansible Project\
**Created:** [January 17, 2014, 4:04pm UTC](https://forum.ansible.com/t/recap-of-failed-tasks/14366 "2014-01-17T16:04:27Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jerome\_Wagner](https://avatars.discourse-cdn.com/v4/letter/j/76d3ee/32.png) [@Jerome\_Wagner](https://forum.ansible.com/u/Jerome_Wagner)\
**Post date:** [January 17, 2014, 4:04pm UTC](https://forum.ansible.com/t/recap-of-failed-tasks/14366/1 "2014-01-17T16:04:27Z")

</div>

Hello,

Is there an easy way to run a playbook and have a recap with the name of the failed task on a host when a host fails ?

currently the digest says that a host has failed but does not recap why. usually it is way up and lost in the console so you can’t even go back and find it.

Thanks  
Jerome

---

<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:** [January 17, 2014, 4:13pm UTC](https://forum.ansible.com/t/recap-of-failed-tasks/14366/2 "2014-01-17T16:13:21Z")

</div>

You could increase your scrollback or tee to a logfile.

AWX is also great at recording history and you can look at past events per job on a host by host basis.

---

<div class="post-metadata">

**Author:** ![Brian\_Coca1](https://avatars.discourse-cdn.com/v4/letter/b/278dde/32.png) [@Brian\_Coca1](https://forum.ansible.com/u/Brian_Coca1)\
**Post date:** [January 17, 2014, 4:20pm UTC](https://forum.ansible.com/t/recap-of-failed-tasks/14366/3 "2014-01-17T16:20:55Z")

</div>

I use the logfile callback plugin and just look at ~/ansible.log

---

<div class="post-metadata">

**Author:** ![sivel](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/sivel/32/1198_2.png) [@sivel](https://forum.ansible.com/u/sivel)\
**Post date:** [January 17, 2014, 4:26pm UTC](https://forum.ansible.com/t/recap-of-failed-tasks/14366/4 "2014-01-17T16:26:39Z")

</div>

Callbacks are a good way to handle it. I had a callback that tracked that and summarized at the end.

I ended up removing that portion of the code before it hit our git repo, but it was pretty easy to implement.