Hi Team,
I was testing a long running powershell script via the script console. It appears that the script continues to execute over 5mins the task is shown as failed despite providing a custom timeout value.
Version Octopus Deploy 2.6.4.951
You can see the custom value is not present when you view the RAW log from the task.
E.g.
Task ID: ServerTasks-24575
Task status: Failed
Task queued: Wednesday, 3 June 2015 2:31 PM
Task started: Wednesday, 3 June 2015 2:31 PM
Task duration: 5 minutes
| Failed: Script run from management console
14:31:49 Info | Running script on 1 machines.
14:31:49 Verbose | TentacleTimeout set at 00:05:00
14:31:49 Info | The script will run on the following machines:
Hi Evan,
Thanks for getting in touch! This is a known issue that you can track here: https://github.com/OctopusDeploy/Issues/issues/1531
We are going to fix it for 3.0, as we have a lock on fixes for 2.6 this close to our public beta for 3.0.
Thanks for reporting the bug.
Vanessa