Answers: <p>For example, the play below</p>
  <pre class="lang-yaml prettyprint-override"><code>- hosts: localhost
    tasks:
  
      - name: Task will be SKIPPED
        debug:
          msg: You will never see this message.
        when: false
  
      - name: Failed command will be IGNORED
        command: /usr/bin/false
        ignore_errors: true
  
      - name: Failed command will be RESCUED
        block:
          - command: /usr/bin/false
        rescue:
          - debug:
              msg: &quot;{{ ansible_failed_result }}&quot;
  </code></pre>
  <p>gives</p>
  <pre class="lang-yaml prettyprint-override"><code>PLAY RECAP *******************************************************************
  localhost: ok=2 changed=1 unreachable=0 failed=0 skipped=1 rescued=1 ignored=1
  </code></pre>
  <p>For details see</p>
  <ul>
  <li><a href="https://docs.ansible.com/ansible/latest/user_guide/playbooks_error_handling.html#error-handling-in-playbooks" rel="noreferrer">Error handling in playbooks</a></li>
  <li><a href="https://docs.ansible.com/ansible/latest/user_guide/playbooks_blocks.html#handling-errors-with-blocks" rel="noreferrer">Handling errors with blocks</a></li>
  </ul>
  <p>Briefly, an error is ignored when you set <code>ignore_errors: true</code>. This can be set on multiple levels. See <a href="https://docs.ansible.com/ansible/latest/reference_appendices/playbooks_keywords.html#playbook-keywords" rel="noreferrer">Playbook Keywords</a>. If you use <code>block/rescue</code> you can actively handle the consequences of the error.</p>
  
Answers: CC BY-SA 4.0
Answers: 2021-08-20T03:15:42.227Z
Answers: Thank you very much. Very clear now to me.
Answers: Alic Antunez Cruz
Answers: CC BY-SA 4.0
Answers: 2021-08-18T04:07:35.583Z
Answers: 2021-08-18T04:29:54.237Z
Answers: 2021-08-18T04:29:54.237Z
Answers: Vladimir Botka
Body: <p>What do skipped, rescued, and ignored results mean in an Ansible playbook execution?
  What would be a possible scenario where these results would be different from 0?</p>
  <pre class="lang-yaml prettyprint-override"><code>PLAY RECAP *******************************************************************
  localhost: ok=3 changed=1 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0
  </code></pre>
  
Comments: CC BY-SA 4.0
Comments: 2021-08-18T09:11:14.903Z
Comments: could you please provide a text version of the screenshot, making it easier to read and more accessible? thanks!
Comments: Bruce Becker
Comments: CC BY-SA 4.0
Comments: 2021-08-18T09:20:54.067Z
Comments: I did it. Thank you for having pointed to that.
Comments: Vladimir Botka
Tags: <ansible><automation><networking>
Title: What do skipped, rescued, and ignored results mean in ANSIBLE playbook execution?
UserDisplayName: Alic Antunez Cruz
ThreadText: # What do skipped, rescued, and ignored results mean in ANSIBLE playbook execution?
  
  (Asked by: username_0 on 2021-08-18)
  
  What do skipped, rescued, and ignored results mean in an Ansible playbook execution?
  What would be a possible scenario where these results would be different from 0?
  
  ```yaml
  PLAY RECAP *******************************************************************
  localhost: ok=3 changed=1 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0
  
  ```
  
  **Tags:** ansible, automation, networking
  
  > **Comments:**
  > **username_1**: could you please provide a text version of the screenshot, making it easier to read and more accessible? thanks!  
  > **username_2**: I did it. Thank you for having pointed to that.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2021-08-18. Score: 5
  
  For example, the play below
  
  ```yaml
  - hosts: localhost
    tasks:
  
      - name: Task will be SKIPPED
        debug:
          msg: You will never see this message.
        when: false
  
      - name: Failed command will be IGNORED
        command: /usr/bin/false
        ignore_errors: true
  
      - name: Failed command will be RESCUED
        block:
          - command: /usr/bin/false
        rescue:
          - debug:
              msg: "{{ ansible_failed_result }}"
  
  ```
  
  gives
  
  ```yaml
  PLAY RECAP *******************************************************************
  localhost: ok=2 changed=1 unreachable=0 failed=0 skipped=1 rescued=1 ignored=1
  
  ```
  
  For details see
  
  * [Error handling in playbooks](https://docs.ansible.com/ansible/latest/user_guide/playbooks_error_handling.html#error-handling-in-playbooks)
  * [Handling errors with blocks](https://docs.ansible.com/ansible/latest/user_guide/playbooks_blocks.html#handling-errors-with-blocks)
  
  Briefly, an error is ignored when you set `ignore_errors: true`. This can be set on multiple levels. See [Playbook Keywords](https://docs.ansible.com/ansible/latest/reference_appendices/playbooks_keywords.html#playbook-keywords). If you use `block/rescue` you can actively handle the consequences of the error.
  
  > **Comments:**
  > **username_0**: Thank you very much. Very clear now to me.  
  
  ---
  
  