Using ansible often relies on a property called "idempotence". If you apply a role a second time, it's expected to have the same result. E.g. it won't add a second copy of the same line in a config file.
There's another property you might call "resumable". In the event of a network partition between controller and target, can an interrupted play be re-run when the partition is resolved?
Ansible hints towards this property, by listing failed targets & allowing them to be re-tried.
However if you review the practical examples, they do not appear to hold this property. Suggest an approach which will ensure I recognize any failures of my playbooks to resume correctly.
- name: Create Mysql configuration file template: src=my.cnf.j2 dest=/etc/my.cnf notify: - restart mysql - name: Start Mysql Service service: name=mysqld state=started enabled=yes
E.g. the above snippet from ansible-examples, fails to achieve the "resumable" property. The handler "restart mysql" will never trigger, if the play is interrupted after creating the config file but before running the handler "restart mysql".