The enumeration for this is "Low". Having changed the value to 4 (or "Normal" per this reference) and reimported he found the script associated with the job now ran as expected. Wondering how we could handle this7
programatically we found this link:
[MSH] How to change a Processs Priorityfrom the days of Monad. Taking his suggestion one step further I came up with this:
Using the $pid to automatically refer to the instance of PowerShell running my script I can handle this in a single line rather than having to export/manipulate XML or task objects.(Get-Process -id $pid).PriorityClass = "Normal"