nextflow-io/nextflow

Add error strategy shortcuts

Open

#563 opened on Jan 10, 2018

View on GitHub
 (10 comments) (0 reactions) (0 assignees)Groovy (3,382 stars) (784 forks)batch import
good first issue

Description

The errorStrategy 'retry' implicitly terminates the execution when a task exceeds the max number of allowed retries.

There are use cases in which the user wants to ignore of finish the workflow execution. This is possible by using a dynamic error strategy (closure). However it would be useful to provide two new synthetic error strategies to simplifies the above use case, such as:

  • retryThenIgnore: task execution is retried in case of error, if the errors exceed the maximum number allowed the task is ignored by applying the ignore error strategy.
  • retryThenFinish: task execution is retried in case of error, if the errors exceed the maximum number allowed the execution is stopped by applying the finish error strategy.

Contributor guide

Tech stack
None
Domain
backend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Familiarity with Nextflow error strategiesBasic Groovy knowledge
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Examine how the existing `errorStrategy` directive processes 'retry', 'ignore', and 'finish' strategies in the Nextflow source code, likely in the workflow execution engine. The issue mentions a dynamic closure workaround, so understanding that implementation will help in adding the shortcuts. Look for classes handling task error handling, possibly in the `nextflow.processor` or similar package.
Add error strategy shortcuts · nextflow-io/nextflow#563 | Good First Issue