Option to skip the check for failed deployments

[jpplaisier]

I noticed every time a deployment fails I need to cleanup the failed deployments from my resource group before the SHR continues replacing session hosts. I replace my session hosts every week and almost every week I need to cleanup multiple failed deployments. Because I am replacing session hosts during the weekend this is a bit annoying because usually I am not working at that time. 99% of the time a deployment fails because of a timeout on Azure and I can ignore the issue. It would be great if there would be an option to ignore failed deployments in the function app environment variables.

[WillyMoselhy]

The reason it stops working on a failed deployment is that it cannot guarantee success, for example, the VM is created but failed at domain join, it will just keep on failing, or worst-case scenario create more VMs that fail and increase the cost.

I would love to discuss with you how we can address this issue, would you mind a Teams meeting?

[jpplaisier]

I understand the reason but for us I would be nice if we could skip it. Happy to discuss this in a teams meeting!

[dynek]

I encountered the same issue and "fixed it" by appending -ErrorAction SilentlyContinue to both Get-SHRSessionHost and Get-SHRRunningDeployment.

Is this something that would be acceptable, in order to avoid having the whole thing fail ?