# Setting worker pool

**URL:** <https://community.seqera.io/t/setting-worker-pool/2665>\
**Category:** Ask for help\
**Tags:** seqera\
**Created:** [May 13, 2026, 8:35am UTC](https://community.seqera.io/t/setting-worker-pool/2665 "2026-05-13T08:35:02Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![dommas](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/dommas/32/2448_2.png) [@dommas](https://community.seqera.io/u/dommas)\
**Post date:** [May 13, 2026, 8:35am UTC](https://community.seqera.io/t/setting-worker-pool/2665/1 "2026-05-13T08:35:03Z")

</div>

Hi, I noticed an undocumented `workerPool` option in the Compute Environment API for Azure Batch.

I recently updated our Seqera integration to use separate node pools for head and compute workloads. Since I couldn’t find a native way to route tasks to a specific pool, I currently inject a Nextflow config override into pipelines with:

```groovy
process.queue = "<compute-pool>"

```

While reviewing the API schema, I noticed that the Compute Environment itself exposes a `workerPool` field, but I couldn’t find any documentation describing its behavior.

Could anyone confirm:

- Does `workerPool` map internally to `process.queue` for task execution?

- Is configuring worker/compute pools through the Compute Environment the intended approach?

- If so, is there any documentation or recommended usage pattern for this feature?

Mentioned option (not to confuse with forge parameter):

 ![Screenshot 2026-05-13 at 09.35.14](https://europe1.discourse-cdn.com/flex013/uploads/seqera/original/2X/f/f939ec55f442c7a1d95f4b319b827727909baf29.png)

---

<div class="post-metadata">

**Author:** ![andrew-dawson-seqera](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/andrew-dawson-seqera/32/1212_2.png) [@andrew-dawson-seqera](https://community.seqera.io/u/andrew-dawson-seqera)\
**Post date:** [May 19, 2026, 7:16pm UTC](https://community.seqera.io/t/setting-worker-pool/2665/2 "2026-05-19T19:16:51Z")

</div>

@dommas - This field is documented [here (Seqera’s canonical API documentation)](https://docs.seqera.io/platform-api/create-compute-env), although it may be hard to see. You have to dig down into the request body to see the description.

 ![Screenshot 2026-05-19 at 3.14.07 PM](https://europe1.discourse-cdn.com/flex013/uploads/seqera/original/2X/e/ece3023f3115301a153d361d3c40749fc1f9234e.png)

---

<div class="post-metadata">

**Author:** ![dommas](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/dommas/32/2448_2.png) [@dommas](https://community.seqera.io/u/dommas)\
**Post date:** [May 20, 2026, 8:55am UTC](https://community.seqera.io/t/setting-worker-pool/2665/3 "2026-05-20T08:55:18Z")

</div>

Thank you, must have had overlooked that.

---

<div class="post-metadata">

**Author:** ![andrew-dawson-seqera](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/andrew-dawson-seqera/32/1212_2.png) [@andrew-dawson-seqera](https://community.seqera.io/u/andrew-dawson-seqera)\
**Post date:** [May 20, 2026, 6:37pm UTC](https://community.seqera.io/t/setting-worker-pool/2665/4 "2026-05-20T18:37:03Z")

</div>

no worries!

---

<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:** [June 19, 2026, 1:50pm UTC](https://community.seqera.io/t/setting-worker-pool/2665/5 "2026-06-19T13:50:42Z")

</div>

Azure Batch compute environments now include:

- Separate head and worker node pools
- Virtual Networks (vnets)
- Managed Identities
- Configurable Nextflow head task resources (CPUs and memory)
- Better control over job and task management
- Configurable OS disk size

Let us know how you get on!