Hello all! I am building seqera platform using the terraform provider. Previously in my company we used the heealx provider but are migrating across! I noticed that the seqera provider does not have an organisation member resource, are we expected to add organisation members manually and not through terraform?

Hi Everyone Part of my pipeline is using sqlite to join some datasets and store the database in a temp directory. I am using AWS Batch and created the computes using seqera platform. Everything was working fine until now i started receiving the following error regarding the disk space, is there a way that I can increase the disk space of the compute? Thanks

sqlite3.OperationalError: database or disk is full
  Fusion Info:
      kernel_version: 6.1
      disk_cache_size: 2652Gb
      max_open_files: 1048576
      instance-type: r6gd.12xlarge
      fusion_version: 2.4.18-c81181e
      clone_namespace: false

I'm trying to setup wave builder to use private registry but it keep going to public one

<http://wave.seqera.io/wt/|wave.seqera.io/wt/>..

and I don't see it build on the private registry . I've this config

profiles {
    remote {
        wave {
            enabled = true
            strategy = 'container'
            build {
                repository = '<http://eu.gcr.io/mycompany|eu.gcr.io/mycompany>'
                cacheRepository = '<http://eu.gcr.io/mycompany|eu.gcr.io/mycompany>'
            }
        }

        k8s {
            namespace = 'tower-nf'
            serviceAccount = 'tower-launcher-sa'
            computeResourceType = 'Job'
            pod = [
                    annotations: [
                      '<http://cluster-autoscaler.kubernetes.io/safe-to-evict|cluster-autoscaler.kubernetes.io/safe-to-evict>': 'false'
                ]
            ]
        }
        process {
            executor = 'k8s'
        }
    }
}

Hi there, is there a way to share a personal workflow run with a co-worker or to a shared workspace? To give them access to the runinfo?

Hi there, I would like to request an evaluation license for the https://github.com/seqeralabs/xpack-google package

Hi! I'm trying to launch a workflow on sequera with the following schema.json, but it does not render in the Seqera UI. I've validated i

{
  "$schema": "<https://json-schema.org/draft/2020-12/schema>",
  "$id": "<https://raw.githubusercontent.com///nextflow_schema.seqera.json>",
  "title": "Lorem ipsum",
  "type": "object",
  "definitions": {
    "config_part_1": {
      "title": "Config part 1",
      "type": "object",
      "properties": {
        "prop_1": {
          "type": "string",
          "default": "foo"
        },
        "prop_2": {
          "type": "string",
          "default": "bar"
        },
        "dataset_1": {
          "type": "string",
          "format": "file-path",
          "mimetype": "text/csv"
        }
      }
    },
    "config_part_2": {
      "title": "Config part 2",
      "type": "object",
      "properties": {
        "prop_3": {
          "type": "integer",
          "default": 5
        },
        "prop_4": {
          "type": "number",
          "default": 0.8
        }
      }
    }
  },
  "properties": {},
  "allOf": [
    {
      "$ref": "#/definitions/config_part_1"
    },
    {
      "$ref": "#/definitions/config_part_2"
    }
  ]
}

I've validated the schema using

% npx ajv-cli validate \
  --spec=draft2020 \
  -s schema.json \
  -d /dev/null \
  --strict=false
unknown format "file-path" ignored in schema at path "#/definitions/config_part_1/properties/dataset_1"
unknown format "file-path" ignored in schema at path "#/definitions/config_part_1/properties/dataset_1"
/dev/null valid

It warns about the "file-path" format, but that's the format to use when loading datasets in Seqera if I'm not mistaken, so that should not be the problem, no?

We'd like to collect enough workflow execution meta data that we can reproduce the same results running outside of seqera, or on a different seqera environment. This would include but not limited to gitrepo, githash, dataset (Let's assume we have the datasets backed up/replicated on whatever platform we're running on), nexftlow version, input params etc... Is there already a way to produce such a file (json preferably)?

I’m having a weird problem where I have a specific pipeline that doesn’t want to communicate with Seqera platform and allow itself to be monitored by it. I have many pipelines on the Platform and all of them I can monitor with the GUI except for one (see thread)

I am wondering if there is a way to view the params files outside the GUI. Example

nextflow run '<https://github.com/sanger-tol/ascc>' -name hungry_kare -params-file '<https://api.cloud.seqera.io/ephemeral/4Vqh-LkZt5PO0OMmjVNciA.json>' -with-tower -r 0.5.3 -profile singularity,test -dump-hashes

I’m trying to debug a pipeline but I literally cannot see

<https://api.cloud.seqera.io/ephemeral/4Vqh-LkZt5PO0OMmjVNciA.json>

unless I open up the Seqera Platform GUI, click “Relaunch” and then see what JSON parameters my pipeline has. Trying to access the file I get an HTTP error

wget <https://api.cloud.seqera.io/ephemeral/4Vqh-LkZt5PO0OMmjVNciA.json>
--2026-02-02 14:38:48--  <https://api.cloud.seqera.io/ephemeral/4Vqh-LkZt5PO0OMmjVNciA.json>
Resolving <http://api.cloud.seqera.io|api.cloud.seqera.io> (<http://api.cloud.seqera.io|api.cloud.seqera.io>)... 35.179.197.5, 3.11.38.17, 18.175.79.222
Connecting to <http://api.cloud.seqera.io|api.cloud.seqera.io> (<http://api.cloud.seqera.io|api.cloud.seqera.io>)|35.179.197.5|:443... connected.
HTTP request sent, awaiting response... 403 Forbidden
2026-02-02 14:38:49 ERROR 403: Forbidden.

I can’t open it even from the Seqera website too when I’m logged in. I feel like if you have a

TOWER_ACCESS_TOKEN

, you should be able to view this file somehow in the terminal no? Maybe there is a way but I just don’t know how to do it. I can’t figure it out with the

tower-cli

tool as well. Does anyone know how to view these params files?

Hello all! I have an interesting problem to share. I have been playing around with organisations in our

dev

Seqera platform and I want to create an organisation with the same name as a now deleted organisation. However Seqera platform tells me an organisation with that name already exists! Has anyone seen this before?

Does anyone know how to solve this error when running

seqera ai

Error: Wrong color format 'dim'

I've a weird glitch with Seqera (see image) where it is saying

Unknown pipeline repository or expired Git credentials: <https://github.com/nf-core/rnaseq>

when I try to modify an existing pipeline, create a new pipeline or

launch a run without a configuration

I get this warning for all of the nf-core repositories. My own repositories are working just fine. Any thoughts why this is suddenly happening?

Has anyone explored alternative solutions to NF tower for tracking nextflow pipelines? Looking at around 100+ runs weekly.

@Phil Ewels is there a Google Cloud equivalent to AWS Fargate? Re: nextflow-io/hello, when I launch this job, it successfully downloads the hello.git repo but fails with:

Error executing process > 'sayHello (1)'

Caused by:
  PERMISSION_DENIED: Request had insufficient authentication scopes.

I'll check credentials. Took about 20 minutes to fail though

Hi, I finding this error from this morning on my HPC:

Failed to send message to <https://api.cloud.seqera.io> -- received
- status code : 403
- response msg: Unexpected response for request <https://api.cloud.seqera.io/trace/5Grkqj91Hi5NXM/complete>
- error cause : -

Tried regenerating the token and didn’t work either has something change in the platform API that could explain this behavior by any chance?

does seqera not handle git submodules? i kept getting a generic "Repository may be corrupted" error. Note: I can run this workflow fine locally via nextflow. Finally i removed the submodule from my repo and that seems to have solved the issue launching the same workflow from the seqera platform. is there a way to use submodules with seqera or is that a no go?

I’m having trouble with timeout issues using the tower agent when trying to run a lot of jobs. Is there a way to increase the timeout time? (See thread)

Hi. The email report of Tower runs has changed recently, making the run name much more prominent. I don’t know how others manage their runs, but typically I don’t remember the run names. I remember the pipeline/repo name and the parameters, which are now only displayed much further down in the email and in small font size. I wonder how others feel.

Hi, is there any way to export the tasks table (bottom of the "tasks" tab in workflow view) to some standard format?

Is there a way to view a log of your seqera platform runs? Inside my launch directory for my tower I get this:

$ nextflow log
It looks like no pipeline was executed in this folder (or execution history is empty)

Is there another way?

Hello I am not sure if this is the place to raise the question but.. after the release my full tests are failing from the same reason https://cloud.seqera.io/orgs/nf-core/workspaces/AWSmegatests/watch/48Q9Hyufz3RrAr/logs . I dont really understand since they were working in my local.

is there any problem with the github token

seq-scm-production

? my pipeline runs are stuck randomly in the pulling step

We tried to run this nf-core/spatialaxe on a publicly available Xenium dataset using Seqera Tower and AWS batch. It seems to run into the following file check error when running on AWS batch with fusion. What could be causing this issue? This has happened with and without

Missing required file(s) in xenium bundle '<s3://xxxx/data/spatial_transcriptomics/xenium/public/mouse/GSE272303-SNCA-tg/Line61nTg_1/outs>': [cell_boundaries.csv.gz, cell_boundaries.parquet, cell_feature_matrix.h5, cell_feature_matrix.zarr.zip, cells.csv.gz, cells.parquet, cells.zarr.zip, experiment.xenium, gene_panel.json, metrics_summary.csv, morphology.ome.tif, morphology_focus/, nucleus_boundaries.csv.gz, nucleus_boundaries.parquet, transcripts.parquet, transcripts.zarr.zip]

Hello- as we continue to ramp up on Seqera Cloud, is there somewhere to find a list of issues and possible workarounds? I'm tripping over an uncaught

at nextflow.cloud.google.secrets.GoogleSecretsProvider.getSecret(GoogleSecretsProvider.groovy:131)

Hello. Does Seqera have anything for interactive downstream analysis of single-cell and spatial data? like a built-in h5ad/AnnData viewer or a way to run Scanpy/Squidpy notebooks directly against pipeline outputs?

Hi there chat, I have a azure batch config which uses different machines types for different processes and looks like this:

process {
        executor  = 'azurebatch'     // Use Azure Batch for this profile
        queue     = 'base'           // Default pool for most processes
        //container = 'ubuntu:latest'  // Specify a default container image

        // Direct assignment for Azure Batch
        withName: 'TOOL|...|OTHER_TOOL' {
          cpus = 32
        }

        withName: 'TOOL2' {
        cpus   = { 15 * task.attempt }
        memory = { 50.GB * task.attempt }
        queue     = 'base_16'         // Use the 'base_16' pool for the functional annotation
        }


        withLabel: 'HEAVY' {
          executor  = 'azurebatch'    
          maxForks  = null            
          //container = 'ubuntu:22.04' 
          queue     = 'heavy'         // Use the 'heavy' pool for the processes with the label 'HEAVY'
        }
      }
    }

This works fine from the CLI. How can I deploy a pipeline with this config in Seqera Platform? When creating compute resources I only see choosing one type of machine or a head and one other type of machine but this here is much more specific.

Got a weird error message. Ran the pipeline last week without any issues, exactly the same command and environment in our HPC.

nextflow run . -with-tower -profile singularity

Sep-29 10:01:19.451 [main] DEBUG nextflow.plugin.PluginsFacade - Plugins resolved requirement=[nf-schema@2.7.2, nf-tower@1.28.2]
....
Sep-29 10:01:20.482 [main] DEBUG nextflow.cli.CmdRun -
  Version: 26.04.6 build 12646
  Created: 09-07-2026 18:49 UTC (20:49 CEST)
  System: Linux 5.14.0-687.29.1.el9_8.x86_64
  Runtime: Groovy 4.0.31 on OpenJDK 64-Bit Server VM 25.0.2-internal-adhoc.conda.src
  Encoding: UTF-8 (UTF-8)
....

Sep-29 10:02:48.607 [Tower-thread] ERROR i.seqera.tower.plugin.TowerObserver - Aborting session due to Seqera Platform telemetry exception - Unexpected HTTP response
- endpoint    : <https://api.cloud.seqera.io/trace/DGwaJZR7HiVf8/progress>
- status code : 400
- response msg: Unexpected error while processing request - Error ID: 5vQeN6ULZe07XnJu7hYay2

nextflow.exception.AbortRunException: Unexpected HTTP response
- endpoint    : <https://api.cloud.seqera.io/trace/DGwaJZR7HiVf8/progress>
- status code : 400
- response msg: Unexpected error while processing request - Error ID: 5vQeN6ULZe07XnJu7hYay2

	at io.seqera.tower.plugin.TowerClient.traceProgress(TowerClient.groovy:151)
	at io.seqera.tower.plugin.TowerObserver.sendTasks0(TowerObserver.groovy:602)
	at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
	at java.base/java.lang.reflect.Method.invoke(Method.java:565)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:343)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:328)
	at groovy.lang.MetaClassImpl.doInvokeMethod(MetaClassImpl.java:1341)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1096)
	at groovy.lang.MetaClassImpl.invokeMethodClosure(MetaClassImpl.java:1019)
	at groovy.lang.MetaClassImpl.doInvokeMethod(MetaClassImpl.java:1215)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1096)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1009)
	at groovy.lang.Closure.call(Closure.java:433)
	at groovy.lang.Closure.call(Closure.java:412)
	at groovy.lang.Closure.run(Closure.java:505)
	at java.base/java.lang.Thread.run(Thread.java:1474)
Sep-29 10:02:48.636 [Tower-thread] DEBUG nextflow.Session - Session aborted -- Cause: Unexpected HTTP response

I've been trying to track down the cause of a client workflow not properly `resume`ing on a Tower installation. I've found something that reliably toggles the behavior, but what confuses me is that if this is the cause, I feel like it'd be a common complaint - yet I can't find anything. Does this ring any bells? 1. Submit workflow to Tower using

tw

CLI & providing a params YAML. Let's say one of those params is

foo = 0.0

2. Later, in Tower UI I do a

resume

on this WF &

Launch

3. In the resumed run, it's actually

foo = 0

and now the hash is different If instead in #1 I set

foo = 0

then it works AOK (which yes, means there's an obvious workaround, but that's not my question)

I believe I"ve found root cause. It looks like NF's internal parser for YAML params and JSON params will wind up with different Java types at times and thus not hash. e.g.

0.4

provided via YAML winds up as

Double(0.4

and JSON gets

BigDecimal(0.4

so if you supply YAML params, and I already suspected Tower's

resume

uses JSON, there you go

Hi, I am wondering if you have a matrix of compatibility, with the minimum and maximum supported version of nextflow in sequera platform. I found this: docs.seqera.io/platform-enterprise/functionality_matrix/overview but it only has the defaults, and a message about possible incompatibilities. Thanks 🙂