- URL:
- https://<root>/system/limits/update
- Methods:
POST- Version Introduced:
- 11.2
Access requirements
Required privileges
The Portal Administrator API requires privilege-based access. An administrator must be assigned a specific user privilege, or role, to access any given endpoint. Listed below are the user privileges or roles an administrator can be assigned that provides access to this endpoint. If multiple privileges are listed, only one needs to be assigned to gain access.
Tokens
This API requires token-based authentication. A token is automatically generated for administrators who sign in to the Portal Administrator API directory's HTML interface. Tokens generated in this way are stored for the entirety of the session.
Those accessing the API directory outside of the HTML interface will need to acquire a session token from the generate operation in the Portal Directory API. For security reasons, all POST requests made to the Portal Administrator API must include a token in the request body.
Description
The update operation updates one or more limits (such as scheduled tasks for ArcGIS Notebook, Workflow Manager, ArcGIS Insights, and geoprocessing service tasks) at an individual user level or for the organization as a whole.
Request parameters
| Parameter | Details |
|---|---|
| A JSON array of limits to be updated. Only limits included in the request will be updated. Syntax Example |
| The category of limits that will be updated. Currently, the only supported category is |
| The response format. The default response format is Values: |
Limits
| Limits | Details |
|---|---|
| The maximum number of scheduled Insight reports that can be created by an individual user. |
| The maximum total number of scheduled Insight reports for an organization. |
| The maximum number of active scheduled notebook tasks that can be owned by an individual user. By default, a user can only own 20 active notebooks tasks. When this limit is reached, the user will not be able to create a new notebook task until one of the notebook tasks change its status from |
| The maximum number of total active scheduled notebook tasks for an organization. By default, an organization is limited to 200 active notebook tasks. When this limit is reached, users will not be able to create any additional notebook tasks. |
| The maximum number of scheduled recurring workflow manager jobs that can be created by an individual user. |
| The maximum total number of scheduled recurring workflow manager jobs for an organization. |
| The number of times a task can fail consecutively before it is switched to a failed state. By default, a task can fail 5 times. When this limit is met, the task is changed from its active state, and the task owner must identify and rectify the issue before switching the task's access back to Active. |
| The total number of runs that are reported and maintained for a scheduled task. By default, only the 30 most recent runs will be maintained. Any tasks that are not within the most recent 30 runs will be permanetly deleted. The number of runs can be increased to a total of 50 runs per scheduled task. |
| The maximum number of active scheduled geoprocessing service tasks that can be owned by an individual user. |
| The maximum total number of active scheduled geoprocessing service tasks for an organization. |
Example usage
The following is a sample POST request for the update operation that demonstrates how to update Execute and Execute:
POST /<context>/portaladmin/system/limits/update HTTP/1.1
Host: organization.example.com
Content-Type:
Content-Length: [ ]
properties=[{"limitName": "ExecuteNotebooksUserLimit","numLimit": 15},{"limitName": "ExecuteNotebooksOrgLimit","numLimit": 45}]&category=ScheduleTask&f=pjsonJSON Response example
{
"status": "success"
}