Skip to main content

CategoryDeleteFailureReason

Why a category in a bulk delete request was not deleted

enum CategoryDeleteFailureReason {
  CATEGORY_NOT_FOUND
  CATEGORY_NOT_EMPTY
  CATEGORY_LOOKUP_INVALID
  CATEGORY_DELETE_FAILED
}

Values​

CategoryDeleteFailureReason.CATEGORY_NOT_FOUND​

No category matched that key for this tenant. Retrying will not change that.

CategoryDeleteFailureReason.CATEGORY_NOT_EMPTY​

The category still has child categories, or products and clusters assigned to it.

Ids are deleted in the order they are given, so a parent sent before its children is refused for children the same request goes on to delete. Send children first, or repeat the request.

CategoryDeleteFailureReason.CATEGORY_LOOKUP_INVALID​

The key could not be used for the requested lookup at all — a non-numeric key for an id lookup, or a sourceId lookup sent without the source it needs. Fix the request rather than retrying it.

CategoryDeleteFailureReason.CATEGORY_DELETE_FAILED​

The category was found and its emptiness check passed, but the delete did not complete.

A category configured as a channel's catalogue root also reports this: the single delete wraps that refusal the same way, and this surface does not claim to tell the two apart.

Member Of​

CategoryDeleteFailure object