Note that pr_sys_workindexerqueue table is corresponds to Lucene search (used as a search library till PRPC 7.1.6) and holds data in an upgraded system (not a fresh installation) till all indexes have been converted to Elastic Search (Introduced from PRPC 717). The user must explicitly re-index from the search landing page to create Elastic Search indices to get this conversion done. Till such time, search will be serviced by the older Apache Lucene library (used as the search library till 7.1.6) and SystemIndexer and SystemWorkIndexer are needed to keep those indices up to date.
Can you please let us know your PRPC version ?
Can you please let us know what error you could see in search landing page ?
For an instance, If the state is shown "Available" and you still get this message means that the index file has not been completely built. Doing a full re-index from the search landing page will fix the issue.
Is the thing you're specifically concerned about the ability to search for data that has been stored in a RichText field or is there another issue where indexing doesn't seem to be working for other data?
You may want to enter an SR for us to look into it more deeply... But just thinking about this, I'm not sure it's going to work. The RichText field is probably a text property... So it's going to be saved into the database with the HTML formatting, which will get indexed along with the text itself. When you search, if there is HTML breaking up the string you're looking for, it may not work.
Looking at the RichText value on the clipboard after it's saved will confirm if the HTML is being saved too. If this is the case, I'm not sure if there is anything we could do.
Are you just looking at the results displayed or are you also clicking Show All Results and looking there? It's possible that it's being returned, but just not in the first set of results given on screen.
In any case, if you believe there to be a bug please open an SR for us to look into it. We'll want to see what the RichText value looks like on the clipboard, and logs where debug is enabled on 'com.pega.pegarules.search.internal.es' and the issue reproduced.