nextflow-io / nextflow-io/nextflow
Add error strategy shortcuts
Nobody has claimed this yet.
- Dominant language
- Groovy
- Stars
- 3.5k
- Forks
- 811
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 61
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 theignoreerror strategy.retryThenFinish: task execution is retried in case of error, if the errors exceed the maximum number allowed the execution is stopped by applying thefinisherror strategy.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the implementation and tests for the errorStrategy option, then trace how retry, ignore, and finish handle task failures and retry limits. Done means retryThenIgnore and retryThenFinish are accepted strategies and apply the specified fallback after the maximum retries, with tests covering both behaviors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100