# \#config

**URL:** https://community.seqera.io/tag/config/41.md

[Latest](https://community.seqera.io/latest.md) · [Categories](https://community.seqera.io/categories.md) · [Tags](https://community.seqera.io/tags.md)

---

## [Modify an input parameter based on another input parameter](https://community.seqera.io/t/modify-an-input-parameter-based-on-another-input-parameter/2770)

<div class="topic-metadata">

**Author:** [@wanamalauasha](https://community.seqera.io/u/wanamalauasha)\
**Replies:** 1\
**Last updated:** [October 1, 2026, 1:26pm UTC](https://community.seqera.io/t/modify-an-input-parameter-based-on-another-input-parameter/2770 "2026-10-01T13:26:33Z")

</div>

Hi! Is it possible to modify an input parameter based on another input parameter? Which is the best way to do it, through the configuration file or directly within the process? In my config file: params { initial\_…

---

## [Handling SLURM Node Evictions in Nextflow: A Simple Retry Strategy](https://community.seqera.io/t/handling-slurm-node-evictions-in-nextflow-a-simple-retry-strategy/2575)

<div class="topic-metadata">

**Author:** [@COASD](https://community.seqera.io/u/COASD)\
**Replies:** 1\
**Last updated:** [May 1, 2026, 11:35pm UTC](https://community.seqera.io/t/handling-slurm-node-evictions-in-nextflow-a-simple-retry-strategy/2575 "2026-05-01T23:35:11Z")

</div>

if, like me, you’re running Nextflow with SLURM on a cluster that experiences node evictions, you probably want a way to automatically rerun jobs when they fail due to eviction. According to the documentation on Spot In…

---

## [Dynamic config in executor](https://community.seqera.io/t/dynamic-config-in-executor/2354)

<div class="topic-metadata">

**Author:** [@Poshi](https://community.seqera.io/u/Poshi)\
**Replies:** 2\
**Last updated:** [September 3, 2025, 1:08pm UTC](https://community.seqera.io/t/dynamic-config-in-executor/2354 "2025-09-03T13:08:46Z")

</div>

Hello! I have a working custom pipeline where the newest linter in VSCode is complaining. The snippet of interest is \<nextflow.config\>: profiles { standard { ... } cluster { process { …

---

## [Process failing to retry on timeout](https://community.seqera.io/t/process-failing-to-retry-on-timeout/2298)

<div class="topic-metadata">

**Author:** [@danross](https://community.seqera.io/u/danross)\
**Replies:** 5\
**Last updated:** [July 23, 2025, 7:08pm UTC](https://community.seqera.io/t/process-failing-to-retry-on-timeout/2298 "2025-07-23T19:08:57Z")

</div>

I’m newish to nextflow and trying to set dynamic resource allocations for my pipeline. However, when one of my processes finishes due to exceeding the given time limit, the Command exit status is ‘-’ and isn’t picked up …

---

## [Multiple publishDir for one process in nextflow config](https://community.seqera.io/t/multiple-publishdir-for-one-process-in-nextflow-config/2197)

<div class="topic-metadata">

**Author:** [@pwolk](https://community.seqera.io/u/pwolk)\
**Replies:** 1\
**Last updated:** [June 17, 2025, 2:30pm UTC](https://community.seqera.io/t/multiple-publishdir-for-one-process-in-nextflow-config/2197 "2025-06-17T14:30:25Z")

</div>

Hi! I want two flags which each should trigger the publication of files with different endings: process { withLabel: "fastqc" { if (params.fastqcrawout != false){ publishDir = \[ path: { "${params.out}/fastqc…

---

## [AWS Batch job stuck at runnable when using a compute environment that would enable use of a GPU (A10) -\> which next step to take?](https://community.seqera.io/t/aws-batch-job-stuck-at-runnable-when-using-a-compute-environment-that-would-enable-use-of-a-gpu-a10-which-next-step-to-take/1202)

<div class="topic-metadata">

**Author:** [@Simon\_Grimm](https://community.seqera.io/u/Simon_Grimm)\
**Replies:** 3\
**Last updated:** [March 27, 2025, 5:33pm UTC](https://community.seqera.io/t/aws-batch-job-stuck-at-runnable-when-using-a-compute-environment-that-would-enable-use-of-a-gpu-a10-which-next-step-to-take/1202 "2025-03-27T17:33:56Z")

</div>

I’m encountering an issue with a fairly simple Nextflow pipeline running on AWS Batch. I’ve set up two AWS Batch queues and configured Nextflow to use them based on process tags. I specified two different queues as I nee…

---

## [Failed to import pandas in python process](https://community.seqera.io/t/failed-to-import-pandas-in-python-process/1033)

<div class="topic-metadata">

**Author:** [@saif\_s](https://community.seqera.io/u/saif_s)\
**Replies:** 3\
**Last updated:** [August 1, 2024, 11:33pm UTC](https://community.seqera.io/t/failed-to-import-pandas-in-python-process/1033 "2024-08-01T23:33:47Z")

</div>

Hello, I have this nf script below that has a simple python process that starts by importing pandas then reading a csv file. The conda environment that I utilize is created is in the config file. However, everytime I ru…

---

## [Is there any comprehensive tutorial on config files/options and how to use them?](https://community.seqera.io/t/is-there-any-comprehensive-tutorial-on-config-files-options-and-how-to-use-them/832)

<div class="topic-metadata">

**Author:** [@A\_AD](https://community.seqera.io/u/A_AD)\
**Replies:** 1\
**Last updated:** [June 10, 2024, 1:47am UTC](https://community.seqera.io/t/is-there-any-comprehensive-tutorial-on-config-files-options-and-how-to-use-them/832 "2024-06-10T01:47:18Z")

</div>

I’m trying to understand config files and profiles and how to set them up and use the different options but its a little confusing because theres just different bits of information and files scattered around. Is there an…

---

## [Is there a way to make custom/additional messages for resource exceeded errors?](https://community.seqera.io/t/is-there-a-way-to-make-custom-additional-messages-for-resource-exceeded-errors/358)

<div class="topic-metadata">

**Author:** [@jfy133](https://community.seqera.io/u/jfy133)\
**Replies:** 2\
**Last updated:** [January 3, 2024, 8:28pm UTC](https://community.seqera.io/t/is-there-a-way-to-make-custom-additional-messages-for-resource-exceeded-errors/358 "2024-01-03T20:28:20Z")

</div>

A common issue reported by various users of various nf-core pipelines is when their particular pipeline run hits a default resource limit (in most cases: the time setting). Unfortunately many users don’t understand what…
