From 7807be0fc37f55847ef4787ff72fbd4ff7861bcc Mon Sep 17 00:00:00 2001 From: "James A. Fellows Yates" Date: Mon, 8 Jul 2024 17:28:00 +0200 Subject: [PATCH 1/3] Link to other docs on the failOnIgnore option Signed-off-by: James A. Fellows Yates --- docs/process.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/process.md b/docs/process.md index 5f18a62bbd..e621fba7d2 100644 --- a/docs/process.md +++ b/docs/process.md @@ -1691,6 +1691,8 @@ To illustrate the differences between error strategies, it can be helpful to ima - `finish`: Nextflow will allow any existing jobs to conclude but not submit any more and report an error - `ignore`: Nextflow will proceed to continue submitting processes for the remaining 95 samples and proceed to completion. Nextflow will ignore the error and report a successful pipeline completion - `ignore` and `workflow.failOnIgnore`: Nextflow will proceed to continue submitting processes for the remaining 95 samples and proceed to completion, then exit with an error status and report the error + +See {ref}`metadata` for more information on `workflow.failOnIgnore`. ::: The `retry` error strategy allows you to re-submit for execution a process returning an error condition. For example: From 5b9f4db0858fabb5c0be8d959a26395cf573a4d5 Mon Sep 17 00:00:00 2001 From: "James A. Fellows Yates" Date: Mon, 8 Jul 2024 17:31:25 +0200 Subject: [PATCH 2/3] Link back failOnIgnore to usage with errorStratgy Signed-off-by: James A. Fellows Yates --- docs/metadata.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/metadata.md b/docs/metadata.md index 4197f7f1ec..efbda912d6 100644 --- a/docs/metadata.md +++ b/docs/metadata.md @@ -63,6 +63,8 @@ The following table lists the properties that can be accessed on the `workflow` ::: : Whether the `workflow.failOnIgnore` config option was enabled. +: See {ref}`errorStrategy` for use-cases of this option. + `workflow.fusion.enabled` : Whether Fusion is enabled. From a9128a9e8721e31927093eff413e94cd738a941b Mon Sep 17 00:00:00 2001 From: "James A. Fellows Yates" Date: Mon, 8 Jul 2024 17:55:28 +0200 Subject: [PATCH 3/3] Fix cross-apge links Co-authored-by: Adam Talbot <12817534+adamrtalbot@users.noreply.github.com> Signed-off-by: James A. Fellows Yates --- docs/metadata.md | 2 +- docs/process.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/metadata.md b/docs/metadata.md index efbda912d6..2294e3cbe9 100644 --- a/docs/metadata.md +++ b/docs/metadata.md @@ -63,7 +63,7 @@ The following table lists the properties that can be accessed on the `workflow` ::: : Whether the `workflow.failOnIgnore` config option was enabled. -: See {ref}`errorStrategy` for use-cases of this option. +: See {ref}`process-error-strategy` for use-cases of this option. `workflow.fusion.enabled` : Whether Fusion is enabled. diff --git a/docs/process.md b/docs/process.md index e621fba7d2..03fcfc457c 100644 --- a/docs/process.md +++ b/docs/process.md @@ -1692,7 +1692,7 @@ To illustrate the differences between error strategies, it can be helpful to ima - `ignore`: Nextflow will proceed to continue submitting processes for the remaining 95 samples and proceed to completion. Nextflow will ignore the error and report a successful pipeline completion - `ignore` and `workflow.failOnIgnore`: Nextflow will proceed to continue submitting processes for the remaining 95 samples and proceed to completion, then exit with an error status and report the error -See {ref}`metadata` for more information on `workflow.failOnIgnore`. +See {ref}`metadata-workflow` for more information on `workflow.failOnIgnore`. ::: The `retry` error strategy allows you to re-submit for execution a process returning an error condition. For example: