Config & Params

The Config tab on the run detail page shows the full Nextflow configuration, parameters, and command line used for a run. Together with the git repo and commit shown in the Workflow Info card, this provides everything needed to reproduce a run.

Command Line

The full nextflow run command line used to launch the workflow. This includes the pipeline path or URL, all - flags, profile selections, and parameter overrides.

Each code block has copy and expand buttons. Copy pastes the content to clipboard; expand opens a full-screen modal for easier reading.

Config

The resolved Nextflow configuration after all config files have been merged (cluster config, pipeline nextflow.config, profile-specific includes, and any -c overrides). This is the final, flattened configuration that Nextflow actually used.

This is useful for verifying that process-level directives (CPU, memory, disk, container) resolved to the expected values. If a process received unexpected resources, compare this config against the pipeline's source config files. See nf-config-resolution for a Claude skill that helps debug config resolution.

Params

The workflow parameters as a JSON object. These are the values passed via -params-file, --param flags, or params {} blocks in the config. They control pipeline behavior — input paths, sample sheets, reference genomes, tool flags, etc.

Reproducing a Run

To reproduce a run: check out the same git commit (shown in Workflow Info), use the same params (copy from here), and submit with the same command line. The Config section confirms the resolved state but is not directly usable as input — it is the output of Nextflow's config resolution, not a config file you can pass back in.