Stay organized with collectionsSave and categorize content based on your preferences.
When the Cloud Search gets a delete item request, it doesn't immediately remove
the entire item. Instead, Cloud Search performs asoft deleteby marking the
item as deleted and removing a subset of item information, such as the ACLs,
content, structured data, and metadata. Other information, such as the item
version, is retained.
If a re-indexing request provides a version greater than the existing value,
re-indexing that item while it is in a soft delete state restores the item.
An item is marked as deleted for 7-10 days after which Cloud Search performs
ahard deleteto permanently delete the item. The item ceases to exist and
its version number no longer refers to that specific item.
Maintain consistent item versions
Your content connector should handle versioning of items.
However, if you delete an item outside of your connector logic usingitems.deleteyou must do one of the following to ensure reindexing can be successful:
Reindex your contentafterthe hard delete (7-10 days).
When manually deleting an item, use the actual item version, which you can
obtain by callingitems.get, instead of a random string, such as "None.".
If you don't follow one of these suggestions, an error occurs during indexing
and indexing fails.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-28 UTC."],[],[],null,["# Handle revisions after manual deletes\n\nWhen the Cloud Search gets a delete item request, it doesn't immediately remove\nthe entire item. Instead, Cloud Search performs a *soft delete* by marking the\nitem as deleted and removing a subset of item information, such as the ACLs,\ncontent, structured data, and metadata. Other information, such as the item\nversion, is retained.\n\nIf a re-indexing request provides a version greater than the existing value,\nre-indexing that item while it is in a soft delete state restores the item.\n\nAn item is marked as deleted for 7-10 days after which Cloud Search performs\na *hard delete* to permanently delete the item. The item ceases to exist and\nits version number no longer refers to that specific item.\n\nMaintain consistent item versions\n---------------------------------\n\nYour content connector should handle versioning of items.\nHowever, if you delete an item outside of your connector logic using\n[items.delete](/workspace/cloud-search/docs/reference/rest/v1/indexing.datasources.items/delete)\nyou must do one of the following to ensure reindexing can be successful:\n\n- Reindex your content *after* the hard delete (7-10 days).\n- When manually deleting an item, use the actual item version, which you can obtain by calling [items.get](/workspace/cloud-search/docs/reference/rest/v1/indexing.datasources.items/get) , instead of a random string, such as \"None.\".\n\nIf you don't follow one of these suggestions, an error occurs during indexing\nand indexing fails."]]
