I have a notebook that scans a large portal site for broken links. On my desktop, this Notebook can sometimes run more than 48 hours. I have moved it to the Notebook Server in my Enterprise deployment. When I created a task to schedule it, the task failed. This message was in the result details:
"The job execution time has exceeded the maximum threshold for a single job. This threshold is set by the maxExecuteNotebookTimeMinutes system property, or 120 minutes if not set."
On the Notebook site, I went to the task and looked its advanced settings. The maximum run time is 1,440 minutes (24 hours). I changed that setting in the System Properties on the Server Admin site to 10,080 minutes (7 days), which is much longer than I should need. But, back on the Portal site, I still can't set the max run time to be more than 1,440. It's like the Portal site isn't updating from the new setting on the Server Admin site.
Both the Portal and Server machines have restarted since I updated the max value.
Is there any way to extend that limit on the Portal task settings? Is there an absolute limit on how large I can set the max value in Server Admin? The extreme run time of this Notebook was one of the reasons why I want to migrate it to Notebook Server.
