Ansible - how are tasks executed on host machine? Manually executing a failed task on host machine to see the output - ansible

Question

One of my ansible tasks is failing without an error trace.The only message was that there was a non-zero return code (caused due to set -e ?) on running the bitbucket diy backup script. This was running earlier but is failing now after making some changes (enabling imdsv2) on the ec2 bitbucket server.
It was recommended that I manually run the task on the host to see if I can get some output, but I find myself needing to recreate the entire directory of shell scripts on the host machine to do that.
So I have 2 questions -
Is there a better way to approach this?
How would I be able to run the task from host machine from the point of failure? Some tasks before it were successful, would ansible create a directory for running tasks? And I can continue there?
Sorry I am really new to ansible, and tried going over the docs, but couldn't find a way to debug this stuff properly.
The debug log on ansible doesn't give any helpful output -
<ip-addr> (1, b'\\r\\n{"changed": true, "stdout": "", "stderr": "", "rc": 22, "cmd": ["/apps/bitbucket/atlassian-bitbucket-diy-backup/bitbucket.diy-backup.sh"], "start": "2023-02-16 22:31:18.187412", "end": "2023-02-16 22:31:18.280648", "delta": "0:00:00.093236", "failed": true, "msg": "non-zero return code", "invocation": {"module_args": {"_raw_params": "/apps/bitbucket/atlassian-bitbucket-diy-backup/bitbucket.diy-backup.sh", "_uses_shell": false, "warn": false, "stdin_add_newline": true, "strip_empty_ends": true, "argv": null, "chdir": null, "executable": null, "creates": null, "removes": null, "stdin": null}}}\\r\\n', b'Shared connection to ip-addr closed.\\r\\n')
<ip-addr> Failed to connect to the host via ssh: Shared connection to ip-addr closed.
<ip-addr> ESTABLISH SSH CONNECTION FOR USER: ubuntu
<ip-addr> SSH: EXEC ssh -C -o ControlMaster=auto -o ControlPersist=60s -o StrictHostKeyChecking=no -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o 'User="ubuntu"' -o ConnectTimeout=10 -o 'ControlPath="/runner/cp/72bdb94d8e"' ip-addr '/bin/sh -c '"'"'rm -f -r /home/ubuntu/.ansible/tmp/ansible-tmp-1676547077.8146338-376-91399646558620/ > /dev/null 2>&1 && sleep 0'"'"''
<ip-addr> (0, b'', b'')
fatal: [ip-addr]: FAILED! => {
"changed": true,
"cmd": [
"/apps/bitbucket/atlassian-bitbucket-diy-backup/bitbucket.diy-backup.sh"
],
"delta": "0:00:00.093236",
"end": "2023-02-16 22:31:18.280648",
"invocation": {
"module_args": {
"_raw_params": "/apps/bitbucket/atlassian-bitbucket-diy-backup/bitbucket.diy-backup.sh",
"_uses_shell": false,
"argv": null,
"chdir": null,
"creates": null,
"executable": null,
"removes": null,
"stdin": null,
"stdin_add_newline": true,
"strip_empty_ends": true,
"warn": false
}
},
"msg": "non-zero return code",
"rc": 22,
"start": "2023-02-16 22:31:18.187412",
"stderr": "",
"stderr_lines": [],
"stdout": "",
"stdout_lines": []
}
PLAY RECAP *********************************************************************
ip-addr : ok=13 changed=2 unreachable=0 failed=1 skipped=0 rescued=0 ignored=0
So I tried manually running the script on the host machine but I'm not sure I did it right. I expected an error trace for the bitbucket diy backup script, added some echo statements to see where it went and doesn't output anything after this line (should ideally output debug)
set -e
echo "start" # manually added
SCRIPT_DIR=$(dirname "$0")
source "${SCRIPT_DIR}/utils.sh"
echo "debug" #manually added