# Process already defined: upgrading to 25.10.0 with strict syntax **URL:** \ **Category:** Ask for help\ **Tags:** nextflow\ **Created:** [October 30, 2025, 9:36pm UTC](https://community.seqera.io/t/process-already-defined-upgrading-to-25-10-0-with-strict-syntax/2437 "2025-10-30T21:36:11Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![sstrong99](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/sstrong99/32/188_2.png) [@sstrong99](https://community.seqera.io/u/sstrong99)\ **Post date:** [October 30, 2025, 9:36pm UTC](https://community.seqera.io/t/process-already-defined-upgrading-to-25-10-0-with-strict-syntax/2437/1 "2025-10-30T21:36:11Z")
i’m working on upgrading a pipeline that ran on nextflow 24.10.3 to 25.10.0 with strict syntax enabled. I’m getting an error ```auto A process named '...' is already defined or included in script: .../.../.nf ``` The workflow in question is pretty simple and only includes the process once. e.g. ```auto include { MY_PROCESS } from './my_process' workflow MY_WORKFLOW { take: ... main: MY_PROCESS() ch_out_1 = MY_PROCESS.out.out1 ch_out_2 = MY_PROCESS.out.out2 emit: out1 = ch_out_1 out2 = ch_out_2 ``` Does something about this syntax need to change for 25.10 and strict syntax? ---
**Author:** ![mahesh.binzerpanchal](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/mahesh.binzerpanchal/32/253_2.png) [@mahesh.binzerpanchal](https://community.seqera.io/u/mahesh.binzerpanchal)\ **Post date:** [October 31, 2025, 10:26am UTC](https://community.seqera.io/t/process-already-defined-upgrading-to-25-10-0-with-strict-syntax/2437/2 "2025-10-31T10:26:22Z")
I don’t see any issue with what you’ve written there. ---
**Author:** ![sstrong99](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/sstrong99/32/188_2.png) [@sstrong99](https://community.seqera.io/u/sstrong99)\ **Post date:** [October 31, 2025, 2:30pm UTC](https://community.seqera.io/t/process-already-defined-upgrading-to-25-10-0-with-strict-syntax/2437/3 "2025-10-31T14:30:15Z")
huh ok. I have so far been unable to create a MWE. I will keep trying. I was hoping others had seen something similar when migrating ---
**Author:** ![sstrong99](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/sstrong99/32/188_2.png) [@sstrong99](https://community.seqera.io/u/sstrong99)\ **Post date:** [October 31, 2025, 4:12pm UTC](https://community.seqera.io/t/process-already-defined-upgrading-to-25-10-0-with-strict-syntax/2437/4 "2025-10-31T16:12:06Z")
I was able to create a MWE. When I do ```auto nextflow run . ``` with the files below, i get the error “A process named ‘PROCESS’ is already defined or included in script: ./subworkflow.nf”. Note that if i move all the subworkflows to be defined in main.nf, instead of in separate files, the workflow runs successfully. [main.nf](https://community.seqera.io/uploads/short-url/tGKBY7nAAj364o7m45X3vc3hEiw.nf) (144 Bytes) [process.nf](https://community.seqera.io/uploads/short-url/dUBXk3IApS1yQijazHF1zmUErMu.nf) (77 Bytes) [subworkflow.nf](https://community.seqera.io/uploads/short-url/4EKFYhereLgV7f1ljBDA5n6Rqi2.nf) (77 Bytes) [subworkflow1.nf](https://community.seqera.io/uploads/short-url/qmifR0gBehNnswgDSl0NTL7K0hZ.nf) (90 Bytes) ---
**Author:** ![sstrong99](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/sstrong99/32/188_2.png) [@sstrong99](https://community.seqera.io/u/sstrong99)\ **Post date:** [November 3, 2025, 3:56pm UTC](https://community.seqera.io/t/process-already-defined-upgrading-to-25-10-0-with-strict-syntax/2437/5 "2025-11-03T15:56:30Z")
> > > \## Bug report > > \### Expected behavior and actual behavior > > When a subworkflow is… used more than once in an workflow, and it is sometimes included from a different subworkflow, it raises the error > \`\`\` > A process named '...' is already defined or included in script > \`\`\` > > \### Steps to reproduce the problem > > decompress \[this MWE\](https://github.com/user-attachments/files/23305873/mwe.zip) > > Run > \`\`\` > NXF\_SYNTAX\_PARSER=v2 nextflow run . > \`\`\` > > \### Program output > > \`\`\` > N E X T F L O W ~ version 25.10.0 > > Launching \`./main.nf\` \[boring\_rutherford\] DSL2 - revision: bb66e6056d > > A process named 'PROCESS' is already defined or included in script: ./mwe/subworkflow.nf > \`\`\` > > \### Environment > > \* Nextflow version: 25.10.0 with NXF\_SYNTAX\_PARSER=v2 > \* Java version: 21.0.2 > \* Operating system: macOS > \* Bash version: GNU bash, version 3.2.57(1)-release (arm64-apple-darwin25) > > \### Additional context > > Note that if i move all the subworkflows to be defined in main.nf, instead of in separate files, the workflow runs successfully. Also, the error only occurs with \`NXF\_SYNTAX\_PARSER=v2\` ---
**Author:** ![bentsherman](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/bentsherman/32/52_2.png) [@bentsherman](https://community.seqera.io/u/bentsherman)\ **Post date:** [November 3, 2025, 4:47pm UTC](https://community.seqera.io/t/process-already-defined-upgrading-to-25-10-0-with-strict-syntax/2437/6 "2025-11-03T16:47:03Z")
Thanks Steven for reporting this and the other withName issue. I think they are both bugs. I will try to sort them out this week, and hopefully include fixes in 25.10.1 ---
**Author:** ![system](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/system/32/2402_2.png) [@system](https://community.seqera.io/u/system)\ **Post date:** [November 10, 2025, 4:47pm UTC](https://community.seqera.io/t/process-already-defined-upgrading-to-25-10-0-with-strict-syntax/2437/7 "2025-11-10T16:47:05Z")
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.