Hi @stevenjwilliams0728
Have you played around with the command_timeout parameter. That has worked for me with very large configs or when pulling show commands at locations where latency is a factor.
In a production environment I currently support where I was getting lots of show commands outside of the US I had that set to 120.
This is an excerpt from ansible.cfg but you can also change it in other places to be more targeted. See the link below for more info.
# Ansible Network Debug and Troubleshooting Guide
# https://docs.ansible.com/ansible/latest/network/user_guide/network_debug_troubleshooting.html
[persistent_connection]
# 30 seconds is the new default but is included here in case adjustments are required. Getting show run and other show commands
# from large switch stacks may require increasing this value. I've found 45 works in many cases where I'm running
# show commands against stacks of 4-5 switch members and I've had to kick this up to 460 for high latency devices
# with very large configurations.
command_timeout = 30
# 30 seconds is the default. Increase if you are accessing network devices across high latency links or devices in a
# different global region
connect_timeout = 30
# 15 seconds is the default.
connect_retry_timeout = 30
https://docs.ansible.com/ansible/latest/network/user_guide/network_debug_troubleshooting.html#command-timeout