Automatic deployment triggers misses a machine when processing

[susanpann]

Severity

Workaround available

Version

2022.4.9997

Latest Version

I could reproduce the problem in the latest build

What happened?

When multiple machines become available for deployment and auto-deploy is triggered, one machine is missed from auto-deploy processing.

In 1 customer report, 1 out of 13 machines were missing. In local repro, 1 out of 5 machines were missing.

Reproduction

1. Create a project with deployment target trigger Machine becomes available for deployment & in the same environment/roles
2. Create & register 5 new tentacles in the same environment and role
3. See results in diagnostics > autodeploy and note missing autodeploy machine

Error and Stacktrace

No response

More Information

Auto-deploy for 5 new tentacles - Machines-106 isn't processed

Workaround

Deploy to target manually

[mjhilton]

The Octopus engineering team has reviewed this issue.
After careful consideration, we’ve classed this low priority. This means we won’t work on it in the near future. We prioritize issues based on the number of people affected, the impact type, and available workarounds. If you’ve encountered this issue and haven’t informed our support team, please email support@octopus.com. Knowing how many people this issue affects helps us determine its priority.