| Previous | Next |
| CI_S_NEW_AUXMETADATA | CI_S_RETRY_DOCUMENT |
CI_S_CLIENT_REQUESTED_ABORT
CI_S_CLIENT_REQUESTED_ABORT reports an intentional stop requested by the client side of the indexing pipeline. The gatherer coordinates protocol handlers, filters, and property extraction; cancellation from that path is different from a filter crash, corrupt index, or unsupported file format.
Trace who requested cancellation and at which indexing stage
- Record the item URL and whether the stop occurred while opening the item, filtering content, or committing extracted data.
- Correlate the status with shutdown, scope changes, explicit crawl cancellation, or extension code that returns a client-abort condition.
- Do not automatically quarantine the document as corrupt; a later crawl can legitimately process the same item if the cancellation cause has disappeared.
The Windows Search indexing model separates URL queuing, crawling, and index update. Cancellation evidence should therefore include the current stage and the component active at the time. If many unrelated documents receive this status together, look for service shutdown or administrative activity. If only one custom data source produces it, instrument the protocol handler and filter lifecycle. The diagnostic action is to identify the cancellation owner, not to rebuild the whole catalog by default.
Indexing process · Search development platform · Change notifications
Looking for a different code? Search another status or error code.