# Callbacks: v2\_runner\_on\_ok vs v2\_playbook\_item\_on\_ok?

**URL:** <https://forum.ansible.com/t/callbacks-v2-runner-on-ok-vs-v2-playbook-item-on-ok/20434>\
**Category:** Ansible Project\
**Created:** [February 3, 2016, 8:24am UTC](https://forum.ansible.com/t/callbacks-v2-runner-on-ok-vs-v2-playbook-item-on-ok/20434 "2016-02-03T08:24:59Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Konstantin\_Suvorov](https://avatars.discourse-cdn.com/v4/letter/k/a87d85/32.png) [@Konstantin\_Suvorov](https://forum.ansible.com/u/Konstantin_Suvorov)\
**Post date:** [February 3, 2016, 8:24am UTC](https://forum.ansible.com/t/callbacks-v2-runner-on-ok-vs-v2-playbook-item-on-ok/20434/1 "2016-02-03T08:24:59Z")

</div>

Hello.

I need to get some feedback from ansible runs. I use custom callbacks for this task.  
Could someone describe difference between **v2\_runner\_on\_ok** vs **v2\_playbook\_item\_on\_ok** methods?

During my test runs I see that the **v2\_runner\_on\_ok** is called when tasks are done, but when is **v2\_playbook\_item\_on\_ok** expected to be called?

Thanks!

---

<div class="post-metadata">

**Author:** ![Brian\_Coca](https://avatars.discourse-cdn.com/v4/letter/b/6de8d8/32.png) [@Brian\_Coca](https://forum.ansible.com/u/Brian_Coca)\
**Post date:** [February 3, 2016, 2:26pm UTC](https://forum.ansible.com/t/callbacks-v2-runner-on-ok-vs-v2-playbook-item-on-ok/20434/2 "2016-02-03T14:26:26Z")

</div>

v2\_playbook\_item\_on\_ok is not called 'yet', it is there as placeholder  
for when we reintroduce returning info per item, currently in 2.0 we  
return all info at the end of the loop, which is not optimal (there  
are open tickets on this issue).