# Forge queue naming and pipeline failover

**URL:** <https://community.seqera.io/t/forge-queue-naming-and-pipeline-failover/940>\
**Category:** Ask for help\
**Tags:** aws, platform\
**Created:** [July 10, 2024, 3:19pm UTC](https://community.seqera.io/t/forge-queue-naming-and-pipeline-failover/940 "2024-07-10T15:19:27Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![jcabraham](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/jcabraham/32/839_2.png) [@jcabraham](https://community.seqera.io/u/jcabraham)\
**Post date:** [July 10, 2024, 3:19pm UTC](https://community.seqera.io/t/forge-queue-naming-and-pipeline-failover/940/1 "2024-07-10T15:19:27Z")

</div>

Forge creates AWS Batch queue and CE names using the format TowerForge-bunchanumbers-head, etc. We have pipelines using fallback strategies which depend on knowing the AWS Batch queue names (e.g. if spot gets pre-empted, move to the ondemand queue). But we can’t intuit what Tower will name the CEs, so each time we create new ones we have to update our Nextflow pipeline code. How should we be doing this?

---

<div class="post-metadata">

**Author:** ![Adam\_Talbot](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/adam_talbot/32/62_2.png) [@Adam\_Talbot](https://community.seqera.io/u/Adam_Talbot)\
**Post date:** [July 11, 2024, 1:34pm UTC](https://community.seqera.io/t/forge-queue-naming-and-pipeline-failover/940/2 "2024-07-11T13:34:14Z")

</div>

The name follows a strict schema based on the provider, for AWS Batch it is `${TOWER_FORGE_PREFIX}-${computeEnvId}`, with an additional suffix of `-head` or `-work` when using spot machines. By default, the prefix is TowerForge, so the resulting compute environments are:

```auto
TowerForge-${computeEnvId}-head
TowerForge-${computeEnvId}-work

```

We have a related open feature request for this [here](https://feedback.seqera.io/feature-requests/p/select-platform-compute-environment-via-nextflow-config-without-retrieving-the-i), where you could select a compute environment via the Seqera Platform name instead of the cloud provider ID. Does this sound like a suitable solution for you?

---

<div class="post-metadata">

**Author:** ![jcabraham](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/jcabraham/32/839_2.png) [@jcabraham](https://community.seqera.io/u/jcabraham)\
**Post date:** [July 11, 2024, 2:01pm UTC](https://community.seqera.io/t/forge-queue-naming-and-pipeline-failover/940/3 "2024-07-11T14:01:29Z")

</div>

Thanks, Adam. It’s asking for a verified [seqera.io](http://seqera.io) email address to proceed. I work for Vertex Pharma, we have a site install of Tower, I’m not sure how to go about this.

---

<div class="post-metadata">

**Author:** ![Adam\_Talbot](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/adam_talbot/32/62_2.png) [@Adam\_Talbot](https://community.seqera.io/u/Adam_Talbot)\
**Post date:** [July 11, 2024, 3:20pm UTC](https://community.seqera.io/t/forge-queue-naming-and-pipeline-failover/940/4 "2024-07-11T15:20:58Z")

</div>

My apologies! It’s been flagged as an internal request. I will get it moved and update here.

The feature request is basically you could use a config like this:

```auto
process {
    queue = 'my-compute-env-name'
}

```

and Seqera Platform would replace it with this under the hood:

```auto
process {
    queue = 'TowerForge-${UUID}-work'
}

```

---

<div class="post-metadata">

**Author:** ![Adam\_Talbot](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/adam_talbot/32/62_2.png) [@Adam\_Talbot](https://community.seqera.io/u/Adam_Talbot)\
**Post date:** [July 11, 2024, 3:25pm UTC](https://community.seqera.io/t/forge-queue-naming-and-pipeline-failover/940/5 "2024-07-11T15:25:05Z")

</div>

Feature request has been moved to public facing, you can find it here:

> **[Select platform compute environment via nextflow config without retrieving...](https://feedback.seqera.io/feature-requests/p/select-platform-compute-environment-via-nextflow-config-without-retrieving-the-i)**
>
> It's quite common to point a Nextflow process at a different compute environment than the one the platform submits to. E.

---

<div class="post-metadata">

**Author:** ![jcabraham](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/jcabraham/32/839_2.png) [@jcabraham](https://community.seqera.io/u/jcabraham)\
**Post date:** [July 11, 2024, 3:31pm UTC](https://community.seqera.io/t/forge-queue-naming-and-pipeline-failover/940/6 "2024-07-11T15:31:44Z")

</div>

That would be ideal. NAturally I’m wondering what the ETA is on that… Thanks!

---

<div class="post-metadata">

**Author:** ![robnewman](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/robnewman/32/92_2.png) [@robnewman](https://community.seqera.io/u/robnewman)\
**Post date:** [July 11, 2024, 3:49pm UTC](https://community.seqera.io/t/forge-queue-naming-and-pipeline-failover/940/7 "2024-07-11T15:49:26Z")

</div>

Hi Jim - please upvote the feature request. Our Product team review all user-submitted feature requests weekly and customer upvotes (among other criteria) help inform our product roadmaps and priority. Additionally, if you upvote you will automatically get an email notification when the request changes state. Thanks!

---

<div class="post-metadata">

**Author:** ![jcabraham](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/jcabraham/32/839_2.png) [@jcabraham](https://community.seqera.io/u/jcabraham)\
**Post date:** [July 11, 2024, 3:57pm UTC](https://community.seqera.io/t/forge-queue-naming-and-pipeline-failover/940/8 "2024-07-11T15:57:42Z")

</div>

I will be voting early and often! Thanks again.