Wave cannot connect wtih my Seqera access token

[Amit_Indap1 (Amit Indap)]

I have been enabling wave and fusion with no problems for over a year. But today, I got this error I can’t figure out:

nextflow run main.nf -entry DEEPVARIANT_ONLY --samplesheet Samplesheets/deepvariant_fill.ss.csv

Generates:

ERROR ~ Error executing process > ‘DEEPVARIANT_ONLY:deepvariant (1)’

Caused by:
Wave invalid response: POST https://wave.seqera.io/v1alpha2/container [400] {“message”:“Missing pairing record for Tower endpoint ‘https://api.cloud.seqera.io’”}

– Check ‘.nextflow.log’ file for details

When I do:

curl -H “Authorization: Bearer $TOWER_ACCESS_TOKEN” https://api.cloud.seqera.io/user

I get:

{
  "user": {
    "id": 14993,
    "userName": "amit-indap1",
    "email": "xxx",
    "firstName": "Amit",
    "lastName": "Indap",
    "organization": null,
    "description": null,
    "avatar": "https://lh3.googleuse[redacted]",
    "avatarId": null,
    "notification": null,
    "termsOfUseConsent": true,
    "marketingConsent": true,
    "lastAccess": "2026-02-10T04:00:15Z",
    "dateCreated": "2024-11-19T16:36:16Z",
    "lastUpdated": "2025-08-15T17:21:42Z",
    "deleted": false
  },
  "needConsent": false,
  "defaultWorkspaceId": "xxx",
  "onboardingWorkspaceId": null
}

Everything was working fine, but I’m finding it really strange wave can’t connect with my tower access token. Any suggestion on how to fix?

[ewels (Phil Ewels)]

Hi @Amit_Indap1,

Apologies about this - looks like you were unlucky and hit a brief service outage that was on our end. We also spotted it and have fixed the issue, Wave should be healthy again and your pipeline / curl commands should be working again as expected.

Sorry for the interruption, let us know if you still have any issues.

Phil

[ewels (Phil Ewels)]

Here’s the related status update page for more details: Seqera - Status

Again, apologies for the inconvenience!

[Amit_Indap1 (Amit Indap)]

That’s no problem, thank you for that status link.

Interestingly, I have been launching from ec2 instance, but able to monitor the pipeline on Seqera platform. But now, I don’t see the url anymore. I ended up getting a new token. Not sure if that has anything to do with it.

[ewels (Phil Ewels)]

I need a bit more info to help sorry (how are you running, what command, how it looked before etc etc). But I suspect it should be unrelated to the Wave thing above..

Phil