We came across a customer scenario where the customer Index BP Scheduling is working fine, but the Index BP count keeps increasing even after several Index BP runs. We could see that the BPMV_REIDX row count
continue to increase and at one point it was over 2 million. Also the index count was increasing by approx 5 - 10 k after each completed run of schedule Index. We increased the index maximum bp´s to index from 5000 to 20000. We then took note of the total of the table and after 2 runs we could see that the index count dropped and after first run, the BPMV_REIDX went from 2 million to 53,000. We checked some old workflow_id´s which were in BPMV_REIDX and found they were all deleted from this table and the ARCHIVE_INFO table showed them all set to ARCHIVE_FLAG -1 and date of null, so now they will get re-indexed correctly.
The Schedule_IndexBusinessProcessService runs every 10 minutes. By default, it is configured to index 5,000 business processes every time it runs, which translates to 720,000 business processes in a 24-hours time span.
If your system is handling a high volume of business processes, you can increase the number of business processes indexed per cycle. You can modify the Schedule_IndexBusinessProcessService business process by modifying variable as shown in the following example: