Skip to main content

ContactDeleteFailureReason

Why a contact in a bulk delete request was not deleted

enum ContactDeleteFailureReason {
  CONTACT_NOT_FOUND_ERROR
  CONTACT_MULTIPLE_FOUND_ERROR
  CONTACT_LOOKUP_INVALID
  CONTACT_DELETE_ERROR
}

Values​

ContactDeleteFailureReason.CONTACT_NOT_FOUND_ERROR​

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

ContactDeleteFailureReason.CONTACT_MULTIPLE_FOUND_ERROR​

The key matched more than one contact, so it does not identify which to delete. Nothing was deleted for it. Narrow a sourceId lookup with a source.

ContactDeleteFailureReason.CONTACT_LOOKUP_INVALID​

The key could not be used for the requested lookup at all — a non-numeric key for an id lookup. Fix the request rather than retrying it.

ContactDeleteFailureReason.CONTACT_DELETE_ERROR​

The contact was found but the delete itself did not complete. The id is safe to retry. The contact's login account, if it has one, is unaffected either way: bulk delete removes contact records, not accounts.

Member Of​

ContactDeleteFailure object