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

Unable to search for work objects when work indexing fails



Unable to search for work objects when work indexing fails. However, rule indexing and rule searches work correctly.

Error Messages

[-threads-1110941258)] [STANDARD] [ ] [PegaRULES:07.10] ( ERROR   - Incremental indexing of 'WORK' entries failed: Indexing request failed. Please contact your system administrator. Indexing request failed. Please contact your system administrator.

Steps to Reproduce

  1. Navigate to Designer Studio > Settings > Search.
  2. Initiate work indexing. Work indexing does not complete.

Root Cause

A defect or configuration issue in the operating environment.
The physical index files are corrupted.


Perform the following local-change:
  1. Ensure that the FTSIncrementalIndexer runs on all nodes. This ensures that Rules, Data, and Work indexes are in synchronization.
  2. Turn off the SystemWorkIndexer and the SystemIndexeragents on all nodes.
  3. Backup the pr_sys_queue_ftsindexer table.
  4. Truncate the pr_sys_queue_ftsindexer table.
  5. Stop the JVM.
  6. Remove all the contents in the WORK search index directory.
    • Below is the structure of the folder:
  7. Start the JVM.
  8. Navigate to the Search landing page and manually start re-indexing WORK-.
  9. Navigate to System Management Application (SMA) and restart the FTSIncremental agent.
  10. Ensure the FTSIncremental agent runs every 60 seconds.
  11. Create and search the newly created work objects.
Suggest Edit

Published January 3, 2019 - 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