# AWX Task failed with more then 5 hosts

**URL:** <https://forum.ansible.com/t/awx-task-failed-with-more-then-5-hosts/10774>\
**Category:** Get Help\
**Tags:** netbox, awx\
**Created:** [November 8, 2024, 8:38am UTC](https://forum.ansible.com/t/awx-task-failed-with-more-then-5-hosts/10774 "2024-11-08T08:38:21Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![bayet](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/bayet/32/4268_2.png) [@bayet](https://forum.ansible.com/u/bayet)\
**Post date:** [November 8, 2024, 8:38am UTC](https://forum.ansible.com/t/awx-task-failed-with-more-then-5-hosts/10774/1 "2024-11-08T08:38:21Z")

</div>

Hello everyone,

I have an Ansible AWX playbook that uses NetBox as a dynamic inventory source of truth (SoT). The playbook is designed to back up my devices and upload the backups to Git. The issue I’m facing is that the playbook works successfully for up to 5 devices. However, when I use a group with more than 5 devices, the playbook fails on one of the tasks, such as copying data to a folder, committing to Git, etc.

Please find my `ansible.cfg` configuration attached.

Does anyone know what could be causing this issue and how I can resolve it?

Thank you!

ansible.cfg  
[defaults]  
inventory = ./netbox\_inventory.yml  
retry\_files\_enabled = False  
gathering = explicit  
host\_key\_checking = False  
connect\_timeout = 60  
force\_valid\_group\_names = silently  
interpreter\_python = auto\_silent  
log\_path = ./ansible.log

[persistent\_connection]  
command\_timeout = 120

---

<div class="post-metadata">

**Author:** ![utoddl](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/utoddl/32/249_2.png) [@utoddl](https://forum.ansible.com/u/utoddl)\
**Post date:** [November 8, 2024, 1:51pm UTC](https://forum.ansible.com/t/awx-task-failed-with-more-then-5-hosts/10774/2 "2024-11-08T13:51:52Z")

</div>

You’ve managed to create a playbook that is sensitive to some combination of `strategy`, `forks`, and batch size/`serial`. There will be lots of hints in [Controlling playbook execution: strategies and more — Ansible Community Documentation](https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_strategies.html), but my guess (based on gut reaction; little else to go on so far) is that you can force some “synchronization points” — i.e. places where you can ensure all hosts get caught up — by splitting your [playbook](https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_intro.html#playbook-execution) into multiple plays. They’ll all still be in one file (the playbook), just as separate plays within that playbook.