# Seqera cloud pipeline gets stuck in runnable

**URL:** <https://community.seqera.io/t/seqera-cloud-pipeline-gets-stuck-in-runnable/1297>\
**Category:** Ask for help\
**Tags:** nextflow, aws, ampliseq\
**Created:** [October 16, 2024, 7:11am UTC](https://community.seqera.io/t/seqera-cloud-pipeline-gets-stuck-in-runnable/1297 "2024-10-16T07:11:29Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Amit\_Indap](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/amit_indap/32/1041_2.png) [@Amit\_Indap](https://community.seqera.io/u/Amit_Indap)\
**Post date:** [October 16, 2024, 7:11am UTC](https://community.seqera.io/t/seqera-cloud-pipeline-gets-stuck-in-runnable/1297/1 "2024-10-16T07:11:29Z")

</div>

Hi,

I set up my credentials to run the nf-core ampliseq pipeline in Seqera cloud. It was much easier setting up Batch on there, than on my own. But strangely the pipeline gets stuck with jobs in RUNNABLE when I get to the steps:

```auto
NFCORE_AMPLISEQ:AMPLISEQ:DADA2_TAXONOMY_WF:DADA2_TAXONOMY (ASV_seqs.fasta,assignTaxonomy.fna)

```

and

```auto
NFCORE_AMPLISEQ:AMPLISEQ:BARRNAPSUMMARY

```

I don’t have an error message technically, but it doesn’t seem to move to RUNNING

---

<div class="post-metadata">

**Author:** ![mribeirodantas](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/mribeirodantas/32/235_2.png) [@mribeirodantas](https://community.seqera.io/u/mribeirodantas)\
**Post date:** [November 15, 2024, 12:15am UTC](https://community.seqera.io/t/seqera-cloud-pipeline-gets-stuck-in-runnable/1297/2 "2024-11-15T00:15:49Z")

</div>

Hi @Amit_Indap ,

Did you try again more recently? Can you confirm you’re still running into this issue?

---

<div class="post-metadata">

**Author:** ![Amit\_Indap](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/amit_indap/32/1041_2.png) [@Amit\_Indap](https://community.seqera.io/u/Amit_Indap)\
**Post date:** [November 27, 2024, 2:51pm UTC](https://community.seqera.io/t/seqera-cloud-pipeline-gets-stuck-in-runnable/1297/3 "2024-11-27T14:51:03Z")

</div>

I added the instance types that can run the processes, and it worked  
Thanks for your help!

---

<div class="post-metadata">

**Author:** ![Shrey\_Chakravorty](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/shrey_chakravorty/32/1908_2.png) [@Shrey\_Chakravorty](https://community.seqera.io/u/Shrey_Chakravorty)\
**Post date:** [July 12, 2025, 3:00pm UTC](https://community.seqera.io/t/seqera-cloud-pipeline-gets-stuck-in-runnable/1297/4 "2025-07-12T15:00:26Z")

</div>

Hi @Amit_Indap ,

I am facing the same issue. Can you please help me?

---

<div class="post-metadata">

**Author:** ![mribeirodantas](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/mribeirodantas/32/235_2.png) [@mribeirodantas](https://community.seqera.io/u/mribeirodantas)\
**Post date:** [August 29, 2025, 12:44pm UTC](https://community.seqera.io/t/seqera-cloud-pipeline-gets-stuck-in-runnable/1297/5 "2025-08-29T12:44:09Z")

</div>

Hi @Shrey_Chakravorty,

Can you share more details about what you did and what you’re running into? When was it the last time you tried and ran into this situation?