We’re reusing an existing batch script by calling it from a Powershell script in a custom deploy script while deploying a nuget package. Everything works fine, but the batch script produces a lot of output to stdout and it’s taking Octopus too long to process it all. (I can see that the batch file completed 45 minutes ago and Octopus is still processing it’s output. This is very uncomfortable during a deployment.) Is it possible to disable Octopus’ output processing for that script? (Ideally the output would still be in the log, but Octopus just wouldn’t waste time processing it.) If not, I can try to prevent the script writing to stdout, but I’d prefer not to modify it.