Evangelos Karatzas
10/01/2026, 10:33 AMmachine god to fix the failing pipelines on AWS :DMaxime Garcia
10/01/2026, 10:33 AMEvangelos Karatzas
10/01/2026, 10:33 AMmachine goddessRike Hanssen
10/01/2026, 10:35 AMEvangelos Karatzas
10/01/2026, 10:35 AMEvangelos Karatzas
10/01/2026, 10:36 AMRike Hanssen
10/01/2026, 10:37 AMEvangelos Karatzas
10/01/2026, 10:39 AM26.04.6Rike Hanssen
10/01/2026, 10:48 AMWhat happened
The run failed at compile time (before any task ran), so progress shows 0 processes. The fatal line:
Missing process or function paramsSummaryLog(...)
-- Check script '.../subworkflows/nf-core/utils_nfschema_plugin/main.nf' at line: 5
That subworkflow does include { paramsSummaryLog } from 'plugin/nf-schema'.
Now the mechanism, from the log and the source at the exact commit (0bad731) that ran:
The pipeline's own nextflow.config pins nf-schema@2.7.2, which does export paramsSummaryLog.
But the run log says: Downloading plugin nf-schema@3.0.0. So the unpinned latest (3.0.0) was loaded instead, and paramsSummaryLog was removed/changed in nf-schema 3.0.0 → "Missing process or function".
Why the pin was ignored
Look at the extra config attached to this launch (the Slack-notification block):
plugins {
id 'nf-slack@0.5.0'
}
This plugins {} block in the launch/workspace config overrode the pipeline's plugins { id 'nf-schema@2.7.2' } block. Result: nf-schema lost its version pin and Nextflow resolved it to the latest release, 3.0.0, which is incompatible with this pipeline revision.
The fix
Add the pipeline's nf-schema pin back into the custom plugins block so both plugins are declared with versions:
plugins {
id 'nf-slack@0.5.0'
id 'nf-schema@2.7.2'
}
Keep the rest of the Slack config as-is. Relaunch with that change and the compile error will go away. (Longer term, the Slack plugins{} snippet lives in the workspace/launch config used across nf-core test runs — anywhere it's injected it needs to carry the matching nf-schema pin, or it will silently un-pin nf-schema for every pipeline it touches.)
so it looks like that this was not an issue until recently, because latest plugin was 2.7.2 but with the new release this is now an issue. I hadn't considered that plugin scopes are not additive but overwriting. will add it my list of thigs to doRike Hanssen
10/01/2026, 10:48 AMMaxime Garcia
10/01/2026, 10:49 AMRike Hanssen
10/01/2026, 10:50 AMRike Hanssen
10/01/2026, 10:53 AMPhil Ewels
10/01/2026, 10:53 AMRike Hanssen
10/01/2026, 10:54 AMMaxime Garcia
10/01/2026, 10:54 AMNicolas Vannieuwkerke
10/01/2026, 10:59 AMRike Hanssen
10/01/2026, 11:01 AMRike Hanssen
10/01/2026, 11:05 AMEvangelos Karatzas
10/01/2026, 11:06 AMEvangelos Karatzas
10/01/2026, 11:07 AMRike Hanssen
10/01/2026, 11:07 AMMaxime Garcia
10/01/2026, 11:07 AMMaxime Garcia
10/01/2026, 11:07 AMRike Hanssen
10/01/2026, 11:07 AM