Overview
When the indexer encounters a problematic (e.g. file is corrupted, not found, access is denied, etc.) object the whole indexing process is cancelled. The rest of the objects are not indexed at all and - after the problematic object is checked/removed - the indexing process needs to be started again from the beginning.This issue has been mitigated since version 23.8 onwards. The indexing process tolerates errors and continues until the end, even though problematic objects were encountered during the process.
Further improvements to the issue are coming in later releases. This document will be updated accordingly.
