These are the application exceptions returned by the REST-based API. Other exceptions may be returned from ALM.
|qccore.bulk-operation-failed||A bulk operation failed, wholly or in part. See Bulk operations.|
|qccore.check-in-failure||Check-in operation failed.|
|qccore.check-out-failure||Check-out operation failed.|
|qccore.entity-not-found||Attempt to access resource that does not exist. For example, querying an entity ID that does not exist in the project.|
|qccore.general-error||The default error thrown on any failure where a specific error cause cannot be identified|
|qccore.invalid-filter-expression||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.
|qccore.invalid-value-type-for-field||Wrong value type for a field. For example, use of a string in an integer field.|
|qccore.lock-failure||Entity may already be locked. Other failure reasons are possible.|
|qccore.operation-forbidden||The logged-on user does not have privileges to perform the action.|
|qccore.required-field-missing||A POST operation failed because data was not passed for a required field.|
|qccore.session-has-expired||Session expired. See Session Management|
|qccore.undo-check-out-failure||Failure cancelling check-out.|
|qccore.unknown-field-name||At least one of the logical field names passed is not defined for the entity.|