Package Acquisition Fails When Using a Scoped Worker Pool Variable with a Git Repository Script Source

[briggs-octo]

Severity

1 report

Version

2025.4.10359, 2026.1.6553

Latest Version

None

What happened?

When using a scoped variable for Worker Pool selection and leveraging a script from a Git repository (as opposed to an inline script), the following error is thrown during package acquisition:

The step failed: No variable named '[WORKER POOL VARIABLE]' was in scope and set to value for '[STEP NAME]' so could not determine which worker pool to use

Reproduction

1. Create a Project.
2. Create a Project Variable of type Worker Pool, assign a Worker Pool, and scope the variable to the Deployment Process for the Project.
3. Configure a Run a Script step within the Deployment Process for the Project, and set the script source to Git repository.
4. Set the step to run on a Worker Pool based on a Variable, using the Variable created previously.
5. Run a Deployment and notice the failure during package acquisition when trying to acquire the script for the step.

Worker Pool Variable scoped to the Deployment Process:

Deployment Process with a Run a Script Step, using a script from a Git repository and running on a Worker/Worker Pool based on the Variable:

Run a Deployment, and see the following error during package acquisition:

Error and Stacktrace

The step failed: No variable named '[WORKER POOL VARIABLE]' was in scope and set to value for '[STEP NAME]' so could not determine which worker pool to use

More Information

No response

Workaround

Add a default, non-scoped value for the Worker Pool Variable.