Bulk Index Process stopped automatically after all entries were processed in Windchill PDMLink v12

[XG_10747975]

I am using Windchill PDMLink Release 12.1 and Datecode with CPS 12.1.0.5

Hello,
We recently executed the Bulk Index Process in Windchill 12 and observed that the process stopped automatically after all entries were processed.
Key Observations:
1. In Windchill 10, the Bulk Index Process did not stop automatically—manual intervention was required.
2. In Windchill 12, the process terminates on its own once all items in the queues IndexQueue1 and IndexQueue2 are indexed.
Questions:
• Is this expected behavior in Windchill 12?
• Was this an intentional change (new feature) introduced in Windchill 12?
• Are there any configuration settings that control this behavior?
• Could there be scenarios where the process hangs or fails to stop?
We have this question because currently we have to manage restart the index process manually(twice per day) to avoid impacts new item indexation and search.

[avillanueva · Accepted solution]

For Bulk Indexing, this makes sense. You are triggering the system to reindex objects. Once they've been index, that should stop. New modifications and check in should appear in IndexQueue1 and 2 but disappear quickly as there are updates. There should be no need to continuously bulk index. From the Index Administrator, you might see sometimes items do no get index and you can rerun the Bulk Indexer to clear those out. That's normal maintenance. 

[XG_10747975]

THALES GROUP LIMITED DISTRIBUTION to email recipients

Thanks for the answer. Our problem is the entries in indexQueue1 & indexQueue2 always failed when the bulk index process stopped.

Currently we have to monitoring the indexqueue1&2 and manually restart bulk index process everyday to have new entries indexed.

[XG_10747975]

We got PTC support answer for this topic. The bulk index process are independent with indexQueue, when bulk index process stopped, the index queue 1 & 2 continue working without issue. Our problem is actually a different issue: we always have the remaining entries which not indexed(automatically) on index administrator. we need to investigate further why some objects are not getting indexed and appearing in remaining count on Index Administration page.