Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Rule Search Index is not updated



The Rule Search Index is not updated.

The queue processor page in Admin Studio displays pyFTSIncrementalIndexer in a Failed state.

Error Messages

Error message from the PegaRULES log:

[CHEDULER_THREAD_POOL] [  STANDARD] [                    ] [                    ] (ueueProcessorFailedRunsManager) ERROR   - Unable to re-start failed queue processor pyFTSIncrementalIndexer. Caught exception: Cannot resubmit the run [pyFTSIncrementalIndexer] because some of its partitions are not in end state
java.lang.IllegalStateException: Cannot resubmit the run [pyFTSIncrementalIndexer] because some of its partitions are not in end state

Steps to Reproduce


Root Cause

When a queue processor's Kafka partition ends up in an unknown state, the automatic restart does not clear the partition which results in the exception. Subsequently, the queue processor fails to restart.


Perform the following local-change:

Use the pxStartRunByID API function, and pass it to the failed queue processor's name. This API function resets the state of the partition when it starts the run.


Published January 20, 2020 - Updated December 2, 2021

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us