Hi, today we noticed that using Remove-PSUSchedule no longer works in version 2026.3.2. The following error message appears: (Screenshot)

It works perfectly under version 2026.2.0.
d6a4ccfe-6c94-42ec-b97b-4538b60c1e32.png
c4ba8eeb-d313-407e-af60-bcbc72b6bf14.png
Recommended Answer
@Marco It looks like the problem is that we added SupportsShouldProcess and set the impact to High for this cmdlet in 2026.3. I don't see it in the release notes so I can see why you ran into this. You can work around it by including the -Confirm parameter.
Remove-PSUSchedule -Schedule $job `
-ComputerName $Target `
-AppToken $Token `
-Confirm:$false
The exception is coming from the fact that the job host is not properly processing PromptForChoice, so we end up with an exception rather than a helpful error message. I've opened an issue to fix the host so it is more clear when something like this happens.
Adam Driscoll
PowerShell Expert and Software Architect at Devolutions
@Marco It looks like the problem is that we added SupportsShouldProcess and set the impact to High for this cmdlet in 2026.3. I don't see it in the release notes so I can see why you ran into this. You can work around it by including the -Confirm parameter.
Remove-PSUSchedule -Schedule $job `
-ComputerName $Target `
-AppToken $Token `
-Confirm:$false
The exception is coming from the fact that the job host is not properly processing PromptForChoice, so we end up with an exception rather than a helpful error message. I've opened an issue to fix the host so it is more clear when something like this happens.
Adam Driscoll
PowerShell Expert and Software Architect at Devolutions
Thanks @Adam Driscoll, exactly what was missing. Thank you.