Open Oliversinn opened 5 months ago
Hi @Oliversinn - Thanks for flagging the issue. I agree the workflow should catch this exception and continue with the rest of the workflow. We are currently working on a fix to allow this to happen!
Edit: Deleted original comment also asking for help. Found solution:
Adding the following line to main.nf into prepNextclade process will allow the pipeline to finish with errors:
errorStrategy 'ignore'
Operating System
Windows 10
Other Linux
No response
Workflow Version
v1.1.0
Workflow Execution
EPI2ME Desktop application
EPI2ME Version
v5.1.14
CLI command run
nextflow run epi2me-labs/wf-flu --rbk --fastq ./fastq/pass/ --disable_ping --out_dir resultado/
Workflow Execution - CLI Execution Profile
standard (default)
What happened?
Workflow crashes at
pipeline:prepNextclade
. I think handling the error is correct:But I think it should let the workflow to continue and just flag the barcode that contains the error in the report. I have 95 barcodes, and in every iteration I removed the barcode's folder mentioned in the log (above is
barcode31
) in order to avoid the whole workflow to crash.Relevant log output
Application activity log entry
No response
Were you able to successfully run the latest version of the workflow with the demo data?
yes
Other demo data information
No response