Uncheck "Enable" and it should be fine.
Sorry but I´m pretty sure it´s still hardcoded to 600 and the only way to get around it, is to
activate timeouts while submitting the job and set "wait to render" to a high (but still reasonable) number of minutes (or do it later in the manager interface but when the job is already running it get´s restarted by changing those values, very keen...). If you don´t do it like this (enable that mentioned checkbox which is a "per
this job timeout", a override) you will still have the default timeout of 600.
But this is really something different from the original problem.
Good Luck
« Last Edit: 2016-05-10, 12:41:57 by Frood »

Logged
Never underestimate the power of a well placed level one spell.