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

Re-index ends with "Transitioning from [RUNNING] to [FAILED]."



Users experience empty result set when performing searches in Pega environment.
Attempting to re-index finishes in an error state. "Work index file unavailable or corrupted"

Error Messages

2017-07-06 04:16:35,564 [ PegaRULES-Batch-3] [ STANDARD] [ ] [your_ruleset:01.01.01] (pboard.DirectStreamContainerV7) ERROR your_operator - Problem reading java object from stream for pySummaryCount; substituting dictionary attribute '@Z:u?N:' for invalid stream attribute '@Z:u?N:'

Setting logger for class AbstractIndexer to debug reveals this after the above error.

2017-07-06 07:19:14,035 [ PegaRULES-Batch-4] [ STANDARD] [ ] [your_ruleset:01.01.01] ( DEBUG namratam - Transitioning from [RUNNING] to [FAILED].

Steps to Reproduce

Not Applicable

Root Cause

A defect in Pegasystems’ code or rules

There are several work objects that appear to be corrupted.
The indexes are built, but are incomplete due to the missing work objects that could not be read properly.


The indexing appears to 'fail', but in reality it is intact and can be used successfully.
Suggest Edit

Published August 26, 2017 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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