Skip to content

Commit 65bab59

Browse files
Update demystifying resume blogpost (#76)
Update demystifying Nextflow resume blogpost with the current usage of the `-resume` option, as pointed out in nextflow-io/nextflow#3362 Signed-off-by: Marcel Ribeiro Dantas <[email protected]> Signed-off-by: Marcel Ribeiro Dantas <[email protected]> Co-authored-by: Phil Ewels <[email protected]>
1 parent de37a92 commit 65bab59

File tree

1 file changed

+2
-8
lines changed

1 file changed

+2
-8
lines changed

content/blog/2019/demystifying-nextflow-resume.md

Lines changed: 2 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -79,17 +79,11 @@ TIMESTAMP DURATION RUN NAME STATUS REVISION ID SESSION ID
7979
2019-05-06 12:31:24 17s stupefied_euclid OK b9aefc67b4 4dc656d2-c410-44c8-bc32-7dd0ea87bebf nextflow run rnaseq-nf -resume -with-docker
8080
</pre>
8181
82-
You can use the resume command with either the session ID or the run name to recover a specific execution. For example:
83-
84-
```
85-
$ nextflow run rnaseq-nf -resume mighty_boyd
86-
```
87-
88-
or
82+
You can use the resume command with the session ID to recover a specific execution. For example:
8983
9084
```
9185
nextflow run naseq-nf -resume 4dc656d2-c410-44c8-bc32-7dd0ea87bebf
9286
```
9387
9488
95-
*Stay tuned for part two where we will discuss resume in more detail with respect to provenance and troubleshooting techniques!*
89+
*Stay tuned for part two where we will discuss resume in more detail with respect to provenance and troubleshooting techniques!*

0 commit comments

Comments
 (0)