# Empty results field when inspecting playbook tasks with ansible-navigator

**URL:** <https://forum.ansible.com/t/empty-results-field-when-inspecting-playbook-tasks-with-ansible-navigator/44351>\
**Category:** Get Help\
**Tags:** ansible-navigator, ee\
**Created:** [August 21, 2025, 7:06pm UTC](https://forum.ansible.com/t/empty-results-field-when-inspecting-playbook-tasks-with-ansible-navigator/44351 "2025-08-21T19:06:30Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![netgirard](https://avatars.discourse-cdn.com/v4/letter/n/e8c25b/32.png) [@netgirard](https://forum.ansible.com/u/netgirard)\
**Post date:** [August 21, 2025, 7:06pm UTC](https://forum.ansible.com/t/empty-results-field-when-inspecting-playbook-tasks-with-ansible-navigator/44351/1 "2025-08-21T19:06:31Z")

</div>

Hello, looking for a little direction on what seems like odd behavior in ansible-navigator. I am using ansible-navigator run a playbook in an execution environment. Inspecting one particular task, which is using a custom module, the ‘res’ field is displaying an empty dictionary, but if I register the task output and debug it in the next task, I can see the output, and it seems fine. Any pointers on where to look further to try and figure out why I can’t see the output without a debug task?

Using ansible-navigator 25.5.0  
EE is using ansible-core 2.18.8 and ansible-runner 2.4.1