Recurring Deployments Hanging at Active if Included Computer is Deleted from Target Group

[sync-by-unito]

What You Are Seeing?

When a recurring deployment kicks off, if a computer has been deleted from Chocolatey Central Management prior to its run, some computers will hang in an Active state while the deployment tries to deal with the missing computer.

What is Expected?

I would expect the deployment to skip over any missing computers once the machine contact timeout has lapsed, and the rest of the computers to accept and run the deployment as scheduled, but this is not the case in my testing.

How Did You Get This To Happen? (Steps to Reproduce)

1. Create a deployment plan for anything and set it to a schedule. I set a machine contact timeout of 5 minutes.
2. Include a group with three computers.
3. Move the Deployment Plan to Ready.
4. Run the deployment.
5. Delete the computer in the middle of the group.
6. The first machine finishes without issue; the third machine hangs at the Ready status. The entire Deployment Plan hangs at the Active status. It looks like all the machines before the deleted computer would finish successfully, and all the computers after the deleted computer may hang at Ready. Testing with more computers may provide more information.

System Details

• Operating System: Windows Server 2022 (CCM), Windows 10 and Windows 11 (CCM Clients)
• Windows PowerShell Version: 5.1
• Chocolatey CLI Version: 2.3.0
• Chocolatey Licensed Extension version: 6.2.1
• Chocolatey License type (Professional / Business / ?): BusinessTrial
• Terminal/Emulator: Windows PowerShell

Output Log

chocolatey-agent.log

You can see from the timestamps in the log above that the next computer in the deployment picked up the active Deployment Step, but never completed the deployment. After restarting the agent on this machine, it picked up where it left off and completed, then reported in to CCM with a different start time than before. I have screenshots of before and after the restart of the Chocolatey Agent to confirm this.

## Workarounds
Restarting the Chocolatey Agent on any machines hanging in an Active state will allow them to finish the deployment and report success, although this changes the start time of the deployment to when the restart of the Chocolatey Agent happens, rather than when the initial deployment step is received and activated.

## Proposed Solution
None currently known.

## Related Issues and Tickets
[Zendesk Ticket 23150](https://chocolatey.zendesk.com/agent/tickets/23150)

## Done Checklist
* [ ] Title is suitable for using in Release Notes?



┆Issue is synchronized with this [Gitlab issue](https://gitlab.com/chocolatey/central-management/choco-licensed-management-ui/-/issues/1029) by [Unito](https://www.unito.io)