Setting worker pool

[dommas]

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:

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):

[andrew-dawson-seqera (Andrew Dawson)]

@dommas - This field is documented here (Seqera’s canonical API documentation), although it may be hard to see. You have to dig down into the request body to see the description.

[dommas]

Thank you, must have had overlooked that.

[andrew-dawson-seqera (Andrew Dawson)]

no worries!