diff --git a/knowledge base/cloud computing/aws/ssm.md b/knowledge base/cloud computing/aws/ssm.md
index 89cb4ae..fe532d7 100644
--- a/knowledge base/cloud computing/aws/ssm.md	
+++ b/knowledge base/cloud computing/aws/ssm.md	
@@ -204,7 +204,7 @@ Pitfalls:
   > as. Remote commands will often default to running as the `ssm-agent` user, however this will also depend on how SSM
   > has been configured.
 
-- SSM sessions' duration is limited by SSM's settings.<br/>
+- SSM sessions' duration is limited by SSM's _idle session timeout_ setting.<br/>
   That might impact tasks that need to run for more than said duration.
 
   <details style="padding-bottom: 1em">
@@ -216,6 +216,9 @@ Pitfalls:
 
   </details>
 
+  Consider extending the SSM idle session timeout setting, or using `async` tasks (which come with their own SSM
+  caveats) to circumvent this issue.
+
 - Since [SSM starts shell sessions under `/usr/bin`][gotchas], one must explicitly set Ansible's temporary directory to
   a folder the remote user can write to ([source][ansible temp dir change]).
 
@@ -300,7 +303,7 @@ Pitfalls:
         {{ '"failed": 0, "started": 1, "finished": 0' | regex_escape() }}
     community.postgresql.postgresql_db: { … }
     async: "{{ 60 * 60 * 2 }}"                         #-- wait up to 2 hours ( 60s * 60m * 2h )
-    poll: 0                                            #-- fire and forget; ssm would not check anyways
+    poll: 0                                            #-- fire and forget; ssm would not allow self-checking anyways
     register: dump
     changed_when:
       - dump.rc == 0
diff --git a/snippets/ansible/tasks.yml b/snippets/ansible/tasks.yml
index c1e54dd..370d1ae 100644
--- a/snippets/ansible/tasks.yml
+++ b/snippets/ansible/tasks.yml
@@ -842,8 +842,8 @@
                   --exclude-schema archived
                   --no-publications
                   --format d --jobs $(nproc)
-              async: "{{ 60 * 60 * 2 }}"  # wait up to 12 hours -- 60 secs * 60 mins * 12 hours
-              poll: 0                     # fire and forget, since ssm would not allow self-checking anyways
+              async: "{{ 60 * 60 * 2 }}"                   # wait up to 2 hours -- 60s * 60m * 2h
+              poll: 0                                      # fire and forget; ssm would not allow self-checking anyways
               register: dump
               changed_when:
                 - dump.rc == 0
@@ -853,7 +853,7 @@
               failed_when: dump.rc != 0
             - name: Check on the dump task
               vars:
-                max_wait: "{{ (60 / 5 * 12) | int }}"      # wait up to 12 hours -- 60 mins / (delay/60) * 12 hours
+                max_wait: "{{ (60 * 60 * 12) }}"           # wait for the async task to end
                 ansible_aws_ssm_timeout: "{{ max_wait }}"  # ssm uses a single connection, keep active until the end
                 dump_stdout_as_obj: "{{ dump.module_stdout | regex_search('{.*}') | from_json }}"
                 ansible_job_id: "{{ dump_stdout_as_obj.ansible_job_id }}"
@@ -861,8 +861,8 @@
                 jid: "{{ ansible_job_id }}"
               register: dump_result
               until: dump_result.finished
-              retries: "{{ max_wait }}"
-              delay: 300  # check once every 5 minutes to avoid overloading the ssm agent
+              retries: "{{ max_wait | int }}"
+              delay: 300                                   # check once every 5m to avoid overloading the ssm agent
     - name: RDS-specific operations
       block:
         - name: Create an instance's snapshot