These are the application exceptions returned by the REST-based API. Other exceptions may be returned from ALM.
|A bulk operation failed, wholly or in part. See Bulk operations.
|Check-in operation failed.
|Check-out operation failed.
|Attempt to access resource that does not exist. For example, querying an entity ID that does not exist in the project.
|The default error thrown on any failure where a specific error cause cannot be identified
|Error in filter. Common problems are syntax error, invalid logical names, cross-filter where relation does not exist, filter data not in list linked to field. Other errors are possible.
Use of a value where the field values are limited to a project list, and the supplied value is not in the list. For example, attempt to set a defect status to "Dismissed" in a project where "Dismissed" is not a member of the status list.
|Wrong value type for a field. For example, use of a string in an integer field.
|Entity may already be locked. Other failure reasons are possible.
|The logged-on user does not have privileges to perform the action.
|A POST operation failed because data was not passed for a required field.
|Session expired. See Session Management
|Failure cancelling check-out.
|At least one of the logical field names passed is not defined for the entity.