# Playbook retry support

**URL:** <https://forum.ansible.com/t/playbook-retry-support/17585>\
**Category:** Ansible Developer\
**Created:** [February 20, 2015, 11:18pm UTC](https://forum.ansible.com/t/playbook-retry-support/17585 "2015-02-20T23:18:32Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Huy\_Le](https://avatars.discourse-cdn.com/v4/letter/h/f17d59/32.png) [@Huy\_Le](https://forum.ansible.com/u/Huy_Le)\
**Post date:** [February 20, 2015, 11:18pm UTC](https://forum.ansible.com/t/playbook-retry-support/17585/1 "2015-02-20T23:18:32Z")

</div>

I am thinking of adding support to retry failed hosts in ansible-playbook cli. Is there any reason why we should not support that?

Huy

---

<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 20, 2015, 11:29pm UTC](https://forum.ansible.com/t/playbook-retry-support/17585/2 "2015-02-20T23:29:49Z")

</div>

We have limited retry with do/until but I could see the usefulness for  
those with 'problem hosts' of a 'retries: #' entry at play/task/global  
levels.

---

<div class="post-metadata">

**Author:** ![Cliffano\_Subagio](https://avatars.discourse-cdn.com/v4/letter/c/f1d935/32.png) [@Cliffano\_Subagio](https://forum.ansible.com/u/Cliffano_Subagio)\
**Post date:** [February 21, 2015, 12:17am UTC](https://forum.ansible.com/t/playbook-retry-support/17585/3 "2015-02-21T00:17:49Z")

</div>

+1 .

I had to work with such a system where I had to retry everywhere.  
It’s also handy for another problem I encountered in the past, I wrote a set of Ansible playbooks to interact with a web service where everything is asynchronous and requires status polling everywhere. Having a global retry would’ve simplified those playbooks.