@jordeu any chance you can validate this?

@jordeu any chance you can validate this?

Ok, let me launch a +1h pipeline to validate

I'll merge this, however validation would still be important

Sorry, I couldn't validate before. I've checked with the 25.09.1-edge version, and we are still getting this exception after one hour of running:

WARN  nextflow.fusion.FusionEnvProvider - Unable to validate Fusion license - reason: Unauthorized [401] - Verify you have provided a Seqera Platform valid access token

umm, i've tested locally using a short lived jwt token and it was refreshing correctly

umm, i've tested locally using a short lived jwt token and it was refreshing correctly

Yes, I also tested this part, but not altogether. Not sure what is going on, but that cookie problem might not be the full solution.

Re-opening this, @jorgee can you please have a look (context, @jordeu is reporting the jwt token is not updated with when checking the fusion license)

(oops, this is a PR and it cannot be re-opened)

Looking at this now. Just to check if I correctly understood the issue. Nextflow needs a jwt token for validating the fusion license. This token expires, and the httpx client refreshes it, but something fails after refreshing that we get 401 when checking the license. It can be reproduced running a pipeline with fusion and wave enabled with a duration larger than 1 hour. Is it correct? or do I miss something?

Yeah, but it much simpler using a local platform instance and setting jwt lifespan to a few mins. Let's chat over slack