Possible Bug with 'reduce' Operator in Nextflow – Minimal Reproducible Example Provided

When using the reduce operator within a subworkflow, the subworkflow is being triggered to run even when there are no inputs to initiate it.

I’ve created a GitHub repo with a minimal, reproducible example of the issue. It’s possible I missed something, but it might also point to a potential bug.
Looking forward to thoughts and suggestions:
:link: GitHub - vinegang/debug_reduce_nf