It would be helpful in Jobs with powershell tasks to be able to keep the runspace/state of a powershell task for another powershell task later on in the Job or the same task if it is part of a loop. Lets say that you have opened a TCP connection of some kind, to a database or to an API, within your powershell code. If you could set the powershell task to keep its runspace when you get back to it, you won't have to tear down and build the connection over and over. Is there a way to pass that kind of a connection object between tasks already? If not feel free to move this to Feature Requests.