# Issues with notify chains

**URL:** <https://forum.ansible.com/t/issues-with-notify-chains/12535>\
**Category:** Ansible Project\
**Tags:** ansible-project\
**Created:** [March 19, 2013, 11:39pm UTC](https://forum.ansible.com/t/issues-with-notify-chains/12535 "2013-03-19T23:39:07Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Michael\_DeHaan](https://avatars.discourse-cdn.com/v4/letter/m/c4cdca/32.png) [@Michael\_DeHaan](https://forum.ansible.com/u/Michael_DeHaan)\
**Post date:** [March 19, 2013, 11:39pm UTC](https://forum.ansible.com/t/issues-with-notify-chains/12535/1 "2013-03-19T23:39:07Z")

</div>

There's an open ticket to be able to improve handlers, though what you  
may want to do is use "register" with the result of each task and then

"when\_changed".

It is true that they run in the order defined, that's a feature so the  
order is always predictable.

when\_changed may be what you want.