# Passing more than one var between tasks - how is it done?

**URL:** <https://forum.ansible.com/t/passing-more-than-one-var-between-tasks-how-is-it-done/45236>\
**Category:** Get Help\
**Created:** [February 1, 2026, 12:35pm UTC](https://forum.ansible.com/t/passing-more-than-one-var-between-tasks-how-is-it-done/45236 "2026-02-01T12:35:40Z")\
**Posts on this page:** 1\
**Showing post:** 3

<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:** [February 1, 2026, 3:02pm UTC](https://forum.ansible.com/t/passing-more-than-one-var-between-tasks-how-is-it-done/45236/3 "2026-02-01T15:02:14Z")

</div>

As was said [before](https://forum.ansible.com/t/passing-a-var-between-playbook-tasks/45203/12), `.records` is a list, each item of which contains `.attachments` which is also a list, so to handle it correctly you’ll need to iterate over each `record` × `attachment` combination.

A [typical way](https://docs.ansible.com/projects/ansible/latest/playbook_guide/playbooks_loops.html#stacking-loops-via-include-tasks) to handle nested loops is to use an included tasks file. The first task below just dumps out CR sys\_ids paired with their attachments’ sys\_ids. The second task iterates over each of the CRs.

```yaml
    - name: Dump CRs and Attachments
      ansible.builtin.debug:
        msg: "{{ dcr_new_cr_request_found_out.records
                 | json_query('[].{cr_sysid: sys_id,
                                   cr_attachments: attachments[].sys_id
                                  }'
                             ) }}"
    - name: Handle each CR
      ansible.builtin.include_tasks:
        file: clerambeau370_01_cr.yml
      loop: "{{ dcr_new_cr_request_found_out.records }}"
      loop_control:
        loop_var: cr

```

The included task sees each CR in the variable `cr`, and the debug task there loops over that `cr`’s attachments. Behold:

```yaml
---
# clerambeau370_01_cr.yml
- name: Handle CR attachments
  ansible.builtin.debug:
    msg: "handling CR {{ cr.sys_id }}, Attachment {{ attachment.sys_id }}."
  loop: "{{ cr.attachments }}"
  loop_control:
    loop_var: attachment

```

The output contains

```plaintext
msg: handling CR 34a34e0883f6f210f28198c6feaad380, Attachment fc2b752983bab210f28198c6feaad3a5.
msg: handling CR 34a34e0883f6f210f28198c6feaad380, Attachment 742b752983bab210f28198c6feaad3a7.
msg: handling CR 34a34e0883f6f210f28198c6feaad380, Attachment f82b752983bab210f28198c6feaad3a8.

```

If your initial `results` contained more than one CR, this would still work.

---

_[View the full topic](https://forum.ansible.com/t/passing-more-than-one-var-between-tasks-how-is-it-done/45236)._