This happens with every script, but for example take the script below and then instead of leaving the "Run On" field blank or selecting 'Any Computer' or the actual instance name, -> select 'All Computers'
Script is run on the only node / instance that is configured in PSU
Actual behavior
CPU usage goes to 100% and doesn't let up. Stopping the service doesn't work. Only killing the process and starting the service again brings PSU down to normal
Environment data
PSU 3.7.6
Windows Server 2022
Single instance / not clustered
LiteDB
Connected to git
@adamdriscoll I think there might have been a regression somewhere down the line. I am experiencing the same behaviour on 3.10.2 and 4.2.11 (partially)
4.2.11 -> Script run via Invoke-PSUScript -Queue 'All'
Steps to Reproduce
This happens with every script, but for example take the script below and then instead of leaving the "Run On" field blank or selecting 'Any Computer' or the actual instance name, -> select 'All Computers'
Expected behavior
Actual behavior
Environment data
PSU 3.7.6 Windows Server 2022 Single instance / not clustered LiteDB Connected to git
Visuals