Hi, we have built a nextflow pipeline that is mostly working as expected. Using version 26.04.6 but same was true with previous 26.xx.x versions and we just updated everything to latest version. We are facing 2 issues. # Issue 1: We use a custom.config file to feed parameters to the pipeline. When we change a parameter in that file (with a bash sed command outside the pipeline), we expect that the modules that use this parameter do not use the cached results from the previous runs. Unfortunately it does. We can use the 'cache false' option but we would like to use the cache when no parameter change is made. Is there something we do not understand about this caching mechanism? Would you have suggestions to investigate this in our setup? # Issue 2: We enjoy the short performance summary displayed at the end of each run, ie: Completed at: 28-Jul-2026 193051 Duration : 1h 47m 8s CPU hours : 1.9 Succeeded : 13 But for some reasons it is not always displayed. Some server display it at the end of each run, some do not. The code seems the same (git clone). We believe it is a configuration in nextflow but we can't find where this is set up. Can you help?

For 1: Does the same happen when you use param files: docs.seqera.io/nextflow/cli#… we normally recommend to not set parameters in config files nf-co.re/docs/running/configuration/configuration-options#…

Thank you for your suggestion. We'll look into that.

Issue 2: That summary is a workflow.onComplete {} handler (docs.seqera.io/nextflow/notifications#…), not core Nextflow. “Same clone, differs per server” = it’s coming from config outside the repo, usually ~/.nextflow/config (config merge order: docs.seqera.io/nextflow/config). Check `grep -rn onComplete + ~/.nextflow/config`on each server, or diff nextflow config output between a server that shows it and one that doesn’t. Hope that helps! 🙂

Thx @Alice Fulton I'll look into these "recent" additions and complete my workflow with them