Administer automated workflows with ArcGIS Notebooks
Administrators can manage an organization's automated notebook limits.
Using the Manage tasks window from the ArcGIS Notebook Server home page, administrators can view details, edit, pause and resume, or delete each active notebook task in the site. Administrators and notebook authors with the schedule notebook privilege can view details, edit, pause and resume, or delete a notebook task in the details page of the notebook or in the task pane of the notebook editor.
For more information on scheduled notebook tasks, see the Schedule a notebook task help topic.
Scheduled task limits
There are certain user, organizational, and ArcGIS Notebook Server site (machine) level limits related to scheduled notebook tasks.
Change maximum concurrent automated notebook runs (maxExecuteNotebookContainersPerNode)
When a notebook is run by a scheduled task, webhook, or the Execute Notebook API, ArcGIS Notebook Server automatically opens a new container and runs the notebook without user interaction. By default, ArcGIS Notebook Server is configured to run a maximum of 10 concurrent notebook runs for each Notebook Server machine. Considering the resources (CPU and RAM) available on each machine in the Notebook Server site, an administrator can adust this limit by modifying the maxExecuteNotebookContainersPerNode system property in Notebook Server. Any automated notebook request submitted after this limit is exceeded will be added to a queue and run once the number of automated task runs falls below this limit. Queued tasks will fail if the wait time exceeds the timeout time.
Note:
This does not limit the number of notebooks that are run interactively from the notebook editor.
You can change the maxExecuteNotebookContainersPerNode limit by following the steps below.
Note:
Increasing the limit can result in additional resources used on the Notebook Server machine.
Sign in to your ArcGIS Enterprise portal as an administrator.
Click Settings > Site.
Change the value for the
maxExecuteNotebookContainersPerNodeproperty.Click Save.
Review the warning regarding restarting Notebook Server and click Save and Restart to save the changes.
Maximum active scheduled notebook tasks per user
Each notebook author with the privilege to schedule notebooks can create up to a maximum of 20 active notebook tasks. Once this limit is reached, the user cannot create new scheduled tasks. A new task can be created once an existing task changes from Active to Complete, Failed, or Inactive. This limit can be changed by updating the ExecuteNotebooksUserLimit property using the Update System Limits operation in the ArcGIS Portal Administrator API.
Maximum active scheduled notebook tasks per organization
The maximum number of active scheduled notebook tasks for an organization is limited to 200. This limit represents the total number of active tasks that can be owned by all users across an organization. Once this limit is reached, users cannot create new scheduled notebook tasks. This limit can be changed by updating the ExecuteNotebooksOrgLimit Update System Limits operation in the ArcGIS Portal Administrator API.
Number of results reported for a scheduled task
The results of a task are reported and maintained for 30 runs. Any task runs prior to the most recent 30 runs of a task are permanently deleted. This limit can be changed by updating the TaskRunHistoryCount property using the Update System Limits operation in the ArcGIS Portal Administrator API.
Automatic failure of a task
Any tasks that fail five consecutive times will automatically be switched to a failed state and will no longer run. The task owner must ensure that the notebook can be run successfully without any user interaction before reactivating the task. To ensure that the tasks continue to run, the owner of the task must identify and rectify the failure and change the task to the Active state. This limit can be changed by updating the FailedRunsDisableTask property using the Update System Limits operation in the ArcGIS Portal Administrator API.