Unable to validate Fusion license - reason: Unauthorized [401]

[zinfin (Sandie Peters)]

I’ve been unable to find a solution to the following error when running a Nextflow pipeline through our Cloud Basic Seqera plan. We’re using our own AWS Batch configuration (manual).

WARN: Missing JWT cookie from refresh token response ~ null
WARN: Missing JWT_REFRESH_TOKEN cookie from refresh token response ~ null
WARN: Unable to validate Fusion license - reason: Unauthorized [401] - Verify you have provided a valid Seqera Platform access token

This is a new error we haven’t seen when running other Nextflow pipelines with Seqera. The pipeline where this error occurs is a long running (7+ hours) and appeared one hour into the run. The run completed without failures but some expected outputs were absent. I’ve attached a snapshot of our Fusion usage overview and the log file.

nf-5ThTfRSfZ8Csgf.log (903.3 KB)

Thank you!

[ewels (Phil Ewels)]

Hi @zinfin,

Apologies for the trouble you’re hitting here. The Fusion team have been looking into this and we think we’ve tracked down what might be going wrong. Could you please try running with this as a potential short-term fix?

export TOWER_API_ENDPOINT=https://cloud.seqera.io/api

If that fixes things then we’ll know we’re on the right track (and you’ll be unblocked). We will continue our investigation into why this is happening now and how to ship a longer-term fix.

Phil

[zinfin (Sandie Peters)]

@ewels

export TOWER_API_ENDPOINT=https://cloud.seqera.io/api

Thanks @ewels , that seemed to work. We also noticed that hard coding the token into the nextflow config file also worked.

[ewels (Phil Ewels)]

Great! Thanks for getting back to me.

For what it’s worth, we also think that these logs were probably unrelated to any pipeline failures. It’s good that you reported them as we have tracked down an issue which we’ll solve, but we don’t think that it should have had any functional effect on pipeline runs or outputs.