| Previous | Next |
| CI_S_CLIENT_REQUESTED_ABORT | CI_S_CATALOG_RESET |
CI_S_RETRY_DOCUMENT
CI_S_RETRY_DOCUMENT is a success-class retry signal for the indexing pipeline. It means the client can attempt to crawl the document again, so the item should remain eligible for processing instead of being treated as permanently unfilterable or corrupt.
Preserve the retry reason and avoid a tight recrawl loop
- Log the previous result for the same URL together with the time and retry count.
- Allow the gatherer or caller to reschedule the item; do not immediately spin on the same document in extension code.
- For custom protocol handlers, verify that temporary availability and change-notification logic eventually converge instead of re-enqueuing an unchanged item forever.
Windows Search keeps prioritized URL queues and can receive change notifications from data stores. A retryable document should be correlated with the state that changed between attempts: remote availability, stream readiness, item replacement, or a transient component condition. If the status repeats indefinitely, collect the protocol-handler URL, filter CLSID, and timing between attempts. The status itself is not proof of catalog corruption; the important failure is a retry cycle that never reaches normal indexing or a terminal error.
Indexing queues and crawl stages · Notifying the index of changes · Windows Search overview
Looking for a different code? Search another status or error code.