When my Seqera jobs start running a bit later after launch than usual, due to them waiting for some time on the Slurm queue of our shared computing cluster, by the time they run, the Seqera API ephemeral files have expired and I get this error: ERROR ~ Unable to access config file 'https://api.cloud.seqera.io/ephemeral/XXXX' -- Cause: Server returned HTTP response code: 403 for URL: https://api.cloud.seqera.io/ephemeral/XXXX. How long are these ephemeral files available for, and can their lifetime be increased?
Hi @emmacarli ! Welcome to the community forum 
If I’m not mistaken, these ephemeral files are available for 8 hours. Out of curiosity, what version of Nextflow are you using?
Hello! Thank you for the quick reply. OK, do you know if there is a way to increase their lifetime? The version of Nextflow we are using is 23.10.1.
Currently, the only way to increase it is if you are using Seqera Enterprise, which is on-prem. If that was the case, you could adjust it in your Seqera Enterprise instance. But as it seems to me that you’re running Seqera Cloud, it’s not possible to adjust it, unfortunately.
1 Like