Hi, I have read multiple topics on the executor.jobName issues, and I am not sure if it has been solved. I see this post:
master ← fix-error-executor-jobname
opened 05:27PM - 02 Sep 25 UTC
This PR fixes a false error for the `executor.jobName` config option.
I origi… nally added a check for invalid dynamic config options, since only process config options can be dynamic. However, there are some config options that explicitly expect a closure, like `executor.jobName`.
Instead of adding another special case for this, I will move this check into the language server as part of type checking. So this PR just removes the check in nf-lang to address the false error.
and I am currently running Nextflow v. 25.10.4; however, I am still having issues. Here is my code on nextflow.config:
withLabel: medium_res {
executor = “slurm”
executor.jobName = { “TEST_$task.name” }
cpus = 3
memory = 50.GB
time = 12.h
clusterOptions = “–account=myGroup --qos=myGroup-b”
}
However, the line “executor.jobName “ causes the flllowing error:
WARN: Cannot read project manifest – Cause: No such property: jobName for class: java.lang.String
ERROR ~ No such variable: jobName
Can you please advise?
Best,
Max
I think the problem lies within the withLabel: medium_res {block. If I am not mistaken, you can only write process-related configurations there.
Instead, try a profiles {} block:
profiles {
slurm {
executor = “slurm”executor.jobName = { “TEST_$task.name” }
cpus = 3
memory = 50.GB
time = 12.h
clusterOptions = “–account=myGroup --qos=myGroup-b”
}
}