Admittedly newly returning to nextflow after a long stretch, I'm confusing myself a bit when reading the configuration of profiles and resourceLimits for multiple queues. I'm trying to learn from the explanations and the examples here: nf-co.re/docs/developing/institutional-profiles/configuration#… I understand that

process {
  queue = { task.time <= 24.h ? 'general' : 'long' }
}

will switch queue based on the job duration, while profiles can be used to pick specific partitions to submit jobs to (as explained in this ARCC example)

profiles {
  bigmem {
    process {
      resourceLimits = [
        cpus: 64,
        memory: 4.TB,
        time: 168.h
      ]
      queue = 'bigmem'
    }
  }
}

My question is whether profiles (i.e. resourceLimits) kick in when the queue switches at the process scope, or whether the relevant profiles must be selected at launch, i.e.

nextflow -profile general,long,bigmem

Hi, @Kevin RUE! This looks like a general question and not something specific to an nf-core workflow. Please re-post your question on the Nextflow Community Forum - https://community.seqera.io 🎉

The active

resourceLimits

will be used to cap the resources requested by the process before launching/scheduling it. This is dynamic. Active above will depend on both the general configuration order (https://docs.seqera.io/nextflow/config) and the selector priority (https://docs.seqera.io/nextflow/config#selector-priority).