Remove task attempt from hash list and add note (#6123) [ci skip]

Signed-off-by: Christopher Hakkaart <chris.hakkaart@seqera.io>

Author: christopher-hakkaart

docs/cache-and-resume.md

@@ -30,15 +30,18 @@ The task hash is computed from the following metadata:
 - Any task {ref}`process-ext` properties referenced in the task script
 - Any {ref}`bundled scripts <bundling-executables>` used in the task script
 - Whether the task is a {ref}`stub run <process-stub>`
-- Task attempt
+
+:::note
+Nextflow also includes an incrementing component in the hash generation process, which allows it to iterate through multiple hash values until it finds one that does not match an existing execution directory. This mechanism typically usually aligns with task retries (i.e., task attempts), however this is not guaranteed.
+:::
 
 :::{versionchanged} 23.09.2-edge
 The {ref}`process-ext` directive was added to the task hash.
 :::
 
 Nextflow computes this hash for every task when it is created but before it is executed. If resumability is enabled and there is an entry in the task cache with the same hash, Nextflow tries to recover the previous task execution. A cache hit does not guarantee that the task will be resumed, because it must also recover the task outputs from the [work directory](#work-directory).
 
-Note that files are hashed differently depending on the caching mode. See the {ref}`process-cache` directive for more details.
+Files are hashed differently depending on the caching mode. See the {ref}`process-cache` directive for more details.
 
 ### Task entry