Following consultation with Support, turns out there is a bug in the Powershell Activity that needs to be fixed