How can we help you?

Resolved — New runs stuck in SUBMITTED (2026-11-04): Between approximately 13:39 and 16:30 UTC on November 4, 2026, new pipeline runs launched in Seqera Cloud did not reach their compute environment and remained in the SUBMITTED state. This affected all organizations and compute environment types. New Studio sessions may also have failed to start. Runs already in progress, the web interface and the API were unaffected.
The cause was a single unresponsive SSH host: one compute environment's host accepted a connection but never responded, which stalled the service that submits jobs to compute environments. Queued runs were submitted automatically once the service recovered at 16:30 UTC. A permanent fix was deployed on November 5 at 09:16 UTC, so a single unresponsive host can no longer hold up submissions. We are also working on further changes to isolate compute environments from one another and to detect this kind of stall sooner.
Self-hosted Seqera Platform Enterprise installations were not affected.
No action is required. If a run launched during this period still shows as SUBMITTED, or a Studio did not start, please relaunch it or contact support.

Seqera Enterprise (self-hosted) customers: The legacy distribution endpoint at cr.seqera.io/private is deprecated from Seqera Platform v26.1 onwards.
Only bug fixes for previous major releases will continue to be published there. New releases of Seqera Platform are available from cr.seqera.io/enterprise, which also contains all previous versions of Platform.
Seqera will provide updated credentials for the new endpoint — contact your Seqera representative, or reach out to the support team if you need access.
Customers using cloud.seqera.io are unaffected.