Issue
When using the SharePoint optimized connector with the "Fetch Taxonomy" option enabled, connector jobs may fail or hang indefinitely during execution. This behavior occurs even when running incremental crawls, resulting in unresponsive tasks or job timeouts.
The logs often show repeated entries such as:
This may indicate a backend processing stall related to taxonomy processing or document exporter behavior.
Diagnosis
This issue was confirmed to occur on earlier versions of the SharePoint optimized connector (e.g., 1.0.0 and 1.5.0) when the "Fetch Taxonomy" option is enabled. It may also present in cases where taxonomy fetching is not enabled, indicating a deeper backend or exporter issue in some environments.
Environment
SharePoint Optimized Connector versions 1.0.0 and 1.5.0
Cause
Earlier versions of the SharePoint optimized connector had an issue where taxonomy fetching, especially during incremental crawls, could cause long-running or non-terminating jobs. This was due to delays in the document export pipeline waiting for taxonomy processing to complete, regardless of crawl type.
Resolution
Upgrade the SharePoint optimized connector to version 1.6.0 or later. This version includes fixes for issues related to taxonomy fetching and exporter delays.
Steps
Visit the Lucidworks plugin repository:
https://plugins.lucidworks.com/Download the SharePoint optimized connector version 1.6.0 or later.
Deploy the updated connector in your environment following standard plugin deployment procedures.
Run a full and incremental crawl using the updated connector and confirm that jobs complete successfully.